Re: [DOCS] mistype

On Fri, Aug 25, 2017 at 12:19 PM, wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/sql-expressions.html > Description: > > cite "The restriction about appearing only in the result list or > HAVING > clause applies wi

[DOCS] Mistype

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/9.6/static/sql-createpolicy.html Description: "Note that INSERT with ON CONFLICT DO UPDATE checks INSERT policies' WITH CHECK expressions only for rows appended to the relation by the INSERT

[DOCS] mistype

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/9.6/static/sql-expressions.html Description: cite "The restriction about appearing only in the result list or HAVING clause applies with respect to the query level that the aggregate belongs

Re: [DOCS] Syntax for changing owner on sequence is not correct

I am just telling you that in your officiall documentation i didn't find that command. I founded oj stack owerflow and when i changed command I succesfully changed owner. Also one more hit: documentation will be much better with examples. I am DBA for a 7 years on ms sql and oracle and they have

Re: [DOCS] Failing example for to_number()

Erwin Brandstetter writes: > On 21 August 2017 at 16:30, David G. Johnston > wrote: >> On Mon, Aug 21, 2017 at 5:36 AM, Erwin Brandstetter >> wrote: >>> The example fails for locales where the comma (',') does not happen to be >>> the group separator and the dot ('.') is not the decimal point.

Re: [DOCS] to_char(): 'FM' also suppresses *trailing* zeroes

Erwin Brandstetter writes: > In Table 9-27. "Template Pattern Modifiers for Numeric Formatting" it says: > FM | prefix fill mode (suppress leading zeroes and padding blanks) | FM > In fact, 'FM' also suppresses *trailing* zeroes after the comma. To fix, > this might be changed to: >suppre

Re: [DOCS] Requesting clarifying details on extract(epoch from timestamp)

ralph.h...@gmail.com writes: > Specifically, for the case of 'extract epoch', the docs state: > "for date and timestamp values, the number of seconds since 1970-01-01 > 00:00:00 local time" > I ran an experiment, importing a timestamp '2016-06-26 20:01:38' with > default time zone 'localtime', wh