Re: sepgsql contrib module
Kouhei Kaigai <kaigai@ak.jp.nec.com>
From: KaiGai Kohei <kaigai@ak.jp.nec.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: KaiGai Kohei <kaigai@kaigai.gr.jp>,
PgHacker <pgsql-hackers@postgresql.org>
Date: 2011-01-13T06:10:45Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pgindent run for 9.0, second run
- 239d769e7e05 9.0.0 cited
>> I also think wiki page allows us to brush up the documentation >> rather than exchanging patches effectively. I'll set up a wiki page >> that contains same contents with *.sgml file to revise documentation >> stuff to be included into the *.sgml file finally. How about this idea? > > Sounds good. > I set up a wikipage as a source of *.sgml file. http://wiki.postgresql.org/wiki/SEPostgreSQL_Documentation We can fix up cosmetic things later, so should we review the description of the upcoming official documentation? >> If we use result of the `pg_config --sharedir` here, how about this >> writing style? Or, do we have any other ideas? > > I'm not sure - I'll look at your next draft more closely. > I added a mention about installation path in the "Installation" section, as follows: The following instruction assumes your installation is under the /usr/local/pgsql directory, and the database cluster is in /usr/local/pgsql/data. Substitute your paths appropriately. It seems to me natural rather than using `pg_config --sharedir` instead. (we might need to care about installation path of the pg_config in this case.) Thanks, -- KaiGai Kohei <kaigai@ak.jp.nec.com>