Re: Section 4.1.2.7 contains false information

2019-04-09 Thread David G. Johnston
On Tue, Apr 9, 2019 at 3:03 PM Jind?ich Vavru?ka wrote: > Dear Tom, it works only in psql, it does not work when you talk to the > server using postgresql protocol. That is my point. > > e.g. in the following code the query causes Syntax error (see the text in > red). That means it does not work.

RE: Section 4.1.2.7 contains false information

2019-04-09 Thread Jind?ich Vavru?ka
Dear Tom, it works only in psql, it does not work when you talk to the server using postgresql protocol. That is my point. e.g. in the following code the query causes Syntax error (see the text in red). That means it does not work. Interestingly, when I use $4::timestamp or CAST ( $4 as TIMES

Re: asynchronous commit risk window is overly optimistic

2019-04-09 Thread Bruce Momjian
On Wed, Mar 20, 2019 at 02:50:21PM -0400, Jeff Janes wrote: > https://www.postgresql.org/docs/current/wal-async-commit.html: > > "If the database crashes during the risk window between an asynchronous commit > and the writing of the transaction's WAL records, then changes made during > that > tra

Re: Mark a reloption as indexterm

2019-04-09 Thread Alvaro Herrera
On 2019-Apr-10, Fujii Masao wrote: > Hi, > > I'd like to propose to mark reloptions as indexterms, like GUC, > so that users can more easily search the pages describing > a reloption in document. Attached is the patch which does this. > Is this helpful? Thought? +1 for adding index entries to al

Mark a reloption as indexterm

2019-04-09 Thread Fujii Masao
Hi, I'd like to propose to mark reloptions as indexterms, like GUC, so that users can more easily search the pages describing a reloption in document. Attached is the patch which does this. Is this helpful? Thought? Regards, -- Fujii Masao reloption-doc-v1.patch Description: Binary data

Re: Section 4.1.2.7 contains false information

2019-04-09 Thread Tom Lane
PG Doc comments form writes: > QUOTE: > The CAST() syntax conforms to SQL. The type 'string' syntax is a > generalization of the standard: SQL specifies this syntax only for a few > data types, but PostgreSQL allows it for all types. The syntax with :: is > historical PostgreSQL usage, as is the f

Section 4.1.2.7 contains false information

2019-04-09 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/11/sql-syntax-lexical.html Description: QUOTE: The CAST() syntax conforms to SQL. The type 'string' syntax is a generalization of the standard: SQL specifies this syntax only for a few data t

Confusing information in sections 8.5 and 9.9 (date and time types, functions and operators)

2019-04-09 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/11/datatype-datetime.html Description: Both sections mention syntax TIMESTAMP '2019-01-20 08:00' as valid for input of timestamp data. This seems to work fine in psql, however, this syntax ca

Re: Improve documentation about include_dir parameter.

2019-04-09 Thread Emanuel Araújo
Hi, when I choose conf files instead of postgresql.conf I needed uncomment "include_dir" parameter in postgresql.conf to work fine. It is a exception over defaults parameters in postgresql.conf. Documentation don't explain that. How can submit improve patch in documentation about that. -- *