Re: [DOCS] Manual Entries of commit_delay and commit_siblings are not complete.

2013-01-25 Thread Bruce Momjian
On Tue, Oct 2, 2012 at 05:36:28PM -0700, Tianyin Xu wrote: > Hi, pgsql-docs, > > I was confused by the system behavior of PG's write ahead log, specifically > the > relation between commit_delay, commit_siblings, and fsync. > > Basically according to the manual (http://www.postgresql.org/docs/9

Re: [DOCS] Add clarification example to EXEC SQL CONNECT with password

2013-01-25 Thread Bruce Momjian
On Fri, Jan 25, 2013 at 01:43:59PM -0500, Tom Lane wrote: > Bruce Momjian writes: > > On Fri, Jan 25, 2013 at 01:41:06PM -0500, Tom Lane wrote: > >> It's still completely failing to address the problem that it's formatted > >> as a fourth, independent example. Please remove the blank line. > > >

Re: [DOCS] Add clarification example to EXEC SQL CONNECT with password

2013-01-25 Thread Tom Lane
Bruce Momjian writes: > On Fri, Jan 25, 2013 at 01:41:06PM -0500, Tom Lane wrote: >> It's still completely failing to address the problem that it's formatted >> as a fourth, independent example. Please remove the blank line. > How is this? Yeah, that seems to work --- it looks like a single exa

Re: [DOCS] Add clarification example to EXEC SQL CONNECT with password

2013-01-25 Thread Bruce Momjian
On Fri, Jan 25, 2013 at 01:41:06PM -0500, Tom Lane wrote: > Bruce Momjian writes: > > On Fri, Jan 25, 2013 at 12:50:12PM -0500, Tom Lane wrote: > >> (looks at the whole section) As-is, it's definitely not good, because > >> before there were three independent examples, and now there are three > >>

Re: [DOCS] Add clarification example to EXEC SQL CONNECT with password

2013-01-25 Thread Tom Lane
Bruce Momjian writes: > On Fri, Jan 25, 2013 at 12:50:12PM -0500, Tom Lane wrote: >> (looks at the whole section) As-is, it's definitely not good, because >> before there were three independent examples, and now there are three >> and a half --- the added example depends on the variables declared

Re: [DOCS] Add clarification example to EXEC SQL CONNECT with password

2013-01-25 Thread Bruce Momjian
On Fri, Jan 25, 2013 at 12:50:12PM -0500, Tom Lane wrote: > Bruce Momjian writes: > > On Fri, Jan 25, 2013 at 12:25:32PM -0500, Tom Lane wrote: > >>> ! EXEC SQL CONNECT TO :target USER :user USING :passwd; > >>> ! > >>> ! EXEC SQL CONNECT TO :target USER :user/:passwd; > > >> This sure looks lik

Re: [DOCS] Add clarification example to EXEC SQL CONNECT with password

2013-01-25 Thread Tom Lane
Bruce Momjian writes: > On Fri, Jan 25, 2013 at 12:25:32PM -0500, Tom Lane wrote: >>> ! EXEC SQL CONNECT TO :target USER :user USING :passwd; >>> ! >>> ! EXEC SQL CONNECT TO :target USER :user/:passwd; >> This sure looks like it has broken the intention of the paragraph >> immediately after the

Re: [DOCS] Add clarification example to EXEC SQL CONNECT with password

2013-01-25 Thread Bruce Momjian
On Fri, Jan 25, 2013 at 12:25:32PM -0500, Tom Lane wrote: > Bruce Momjian writes: > > *** a/doc/src/sgml/ecpg.sgml > > --- b/doc/src/sgml/ecpg.sgml > > *** EXEC SQL CONNECT TO unix:postgresql://sq > > *** 194,202 > > EXEC SQL BEGIN DECLARE SECTION; > > const char *target = "m.

Re: [DOCS] Add clarification example to EXEC SQL CONNECT with password

2013-01-25 Thread Tom Lane
Bruce Momjian writes: > *** a/doc/src/sgml/ecpg.sgml > --- b/doc/src/sgml/ecpg.sgml > *** EXEC SQL CONNECT TO unix:postgresql://sq > *** 194,202 > EXEC SQL BEGIN DECLARE SECTION; > const char *target = "m...@sql.mydomain.com"; > const char *user = "john"; > EXEC SQL END DE

Re: [DOCS] Add clarification example to EXEC SQL CONNECT with password

2013-01-25 Thread Bruce Momjian
On Thu, Sep 20, 2012 at 06:17:15PM +0200, Alan B wrote: > Hi list, > Hope this is the right place to suggest that change in the docs, otherwise is > there a ticket management system for this stuff somewhere? > > Paying attention to the documentation at http://www.postgresql.org/docs/8.4/ > static/

Re: [DOCS] Different wording in file_fdw document

2013-01-25 Thread Bruce Momjian
On Wed, Sep 19, 2012 at 08:06:28PM +0900, Shigeru HANADA wrote: > I found the term "foreign data server" in file_fdw document. It doesn't > sound so strange, but "foreign server" or "server" (when context is > clear) are used for same meaning in other places, so users might be > confused by third