Re: [DOCS] Math function description issue

On 8 June 2016 at 00:11, Alvaro Herrera wrote: > Tom Lane wrote: >> =?UTF-8?Q?J=c3=bcrgen_Purtz?= writes: > >> > a) In my opinion this wording is easier to understand because it avoids >> > the negation via "not less". >> >> That's a fair point. >> >>

Re: [DOCS] Math function description issue

Tom Lane wrote: > =?UTF-8?Q?J=c3=bcrgen_Purtz?= writes: > > a) In my opinion this wording is easier to understand because it avoids > > the negation via "not less". > > That's a fair point. > > The other difference is least/greatest versus smallest/largest. I'm not > sure

Re: [DOCS] Math function description issue

=?UTF-8?Q?J=c3=bcrgen_Purtz?= writes: > The standard says: > " computes the least integer greater than or equal to > its argument." Hmm, you're looking at the SQL standard I guess. The existing wording in our docs seems to be taken from the C/POSIX standard, which says

[DOCS] Misleading text mesage

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/7.4/static/jdbc-query.html Description: In https://www.postgresql.org/docs/7.4/static/jdbc-query.html System.out.print(Column 1 returned ); This is good from the POV of the person running

Re: [DOCS] Indicated Epoch 0 is incorrect

The docs are correct. When you convert a string to a timestamp with time zone it will interpret the string in *your* time zone which is apparently offset from UTC. Try: select extract(epoch from timestamp with time zone '1970-01-01 00:00:00-00'); or select extract(epoch from timestamp with time

[DOCS] Copy editing of Dynamic Shared Memory code comments

Couple of typos in src/backend/storage/ipc/dsm.c Will apply if no objection, given vague possibility of change of meaning. -- Simon Riggshttp://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Re: [DOCS] Typo.

2016-06-07 15:44 GMT+03:00 Kevin Grittner : > On Tue, Jun 7, 2016 at 6:26 AM, Dmitry Igrishin wrote: > >> In "Internal position: this is defined the same as the P field, but it >> is used when the cursor position refers to an internally generated", >>

Re: [DOCS] Typo.

On Tue, Jun 7, 2016 at 6:26 AM, Dmitry Igrishin wrote: > In "Internal position: this is defined the same as the P field, but it > is used when the cursor position refers to an internally generated", > "internally generated" should be replaced with "internally-generated". Not

Re: [DOCS] Typo.

2016-06-07 14:26 GMT+03:00 Dmitry Igrishin : > Hi, > > In "Internal position: this is defined the same as the P field, but it > is used when the cursor position refers to an internally generated", > "internally generated" should be replaced with "internally-generated". >

[DOCS] Typo.

Hi, In "Internal position: this is defined the same as the P field, but it is used when the cursor position refers to an internally generated", "internally generated" should be replaced with "internally-generated". https://www.postgresql.org/docs/9.6/static/protocol-error-fields.html -- //

Re: [DOCS] Math function description issue

The standard says: " computes the least integer greater than or equal to its argument." a) In my opinion this wording is easier to understand because it avoids the negation via "not less". b) To dispel the ambiguities concerning what is greater or lesser (with negative numbers) we may add a