Joe Hellerstein's "Looking Back at Postgres" paper

I happened to come across this: https://arxiv.org/pdf/1901.01973 I found this to be really interesting reading, so I wonder if we shouldn't cite it in history.sgml or some such place. regards, tom lane

Re: Chapter "8.8 Geometric Types" of documentation could contain more details

PG Doc comments form writes: > Hi, I am writing to suggest a couple of clarifications to "8.8. Geometric > Types" documentation chapter. Fair points. I am not really eager to say explicitly here that the set of available functions varies for the different types: that seems pretty self-evident.

Re: Document when ssl_prefer_server_ciphers went in

> On 3 Jul 2024, at 18:22, Tom Lane wrote: > > Daniel Gustafsson writes: >> In the documentation for ssl_prefer_server_ciphers we only say it's not in >> "older version" but we omit to specify it further. Since it's a fairly >> important setting for security I think it makes sense to add the ve

Re: Document when ssl_prefer_server_ciphers went in

Daniel Gustafsson writes: > In the documentation for ssl_prefer_server_ciphers we only say it's not in > "older version" but we omit to specify it further. Since it's a fairly > important setting for security I think it makes sense to add the version to > help users, as in the small attached diff

Re: COALESCE documentation

Peter Eisentraut writes: > I think this is actually a bug in the implementation, not in the > documentation. That is, the implementation should behave like the > documentation suggests. The trouble with that is that it presumes that the standard's definition of IS NOT NULL is not broken. I th

Re: COALESCE documentation

On Wed, 2024-07-03 at 11:42 +0200, Navrátil, Ondřej wrote: > On a side note, I tested similar behavior in Oracle databases, and for them, > something like  > select testtype(null, null) is null; -- returns 0 (false) > select testtype(null, null) is not null; -- returns 1 (true) > ...and as far as

Re: COALESCE documentation

On Wednesday, July 3, 2024, Navrátil, Ondřej wrote: > > To get back to my "docs patch proposal" - I could submit a patch if you > would kindly point me where to start. I would also prefer to submit such a > patch only after it is decided whether this is a docs bug or impl bug, and > whether or no

Re: tutorial not accurate

On 02.07.24 22:00, PG Doc comments form wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/tutorial-accessdb.html Description: I was able to create a db (mydb) but when I use any of the test SELECT statements, nothing happens. Her

Chapter "8.8 Geometric Types" of documentation could contain more details

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/datatype-geometric.html Description: Hi, I am writing to suggest a couple of clarifications to "8.8. Geometric Types" documentation chapter. 1. Documentation does not specify what precisi

Re: COALESCE documentation

I do not have the specs on hand. But if the CASE equivalence should hold, then I deduce that COALESCE ( ROW(NULL, 1), ROW(NULL, 2)) results in ROW(NULL, 2) COALESCE ( ROW(NULL, 2), ROW(NULL, 1)) results in ROW(NULL, 1) I understand that order of parameters for coalesce matters for parameters that

tutorial not accurate

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/tutorial-accessdb.html Description: I was able to create a db (mydb) but when I use any of the test SELECT statements, nothing happens. Here is the terminal output when trying your tutoria

Re: Document when ssl_prefer_server_ciphers went in

On 03.07.24 11:23, Daniel Gustafsson wrote: In the documentation for ssl_prefer_server_ciphers we only say it's not in "older version" but we omit to specify it further. Since it's a fairly important setting for security I think it makes sense to add the version to help users, as in the small at

Document when ssl_prefer_server_ciphers went in

In the documentation for ssl_prefer_server_ciphers we only say it's not in "older version" but we omit to specify it further. Since it's a fairly important setting for security I think it makes sense to add the version to help users, as in the small attached diff (which also adds proper markup in

Re: COALESCE documentation

On Wed, 2024-07-03 at 11:00 +0200, Peter Eisentraut wrote: > On 02.07.24 12:45, Navrátil, Ondřej wrote: > > as per documentation > > > > > The |COALESCE| function returns the first of its arguments

Re: COALESCE documentation

On 02.07.24 12:45, Navrátil, Ondřej wrote: Hello, as per documentation > The |COALESCE| function returns the first of its arguments that is not null. Null is returned only if all arguments are n

Re: COALESCE documentation

On Tue, 2024-07-02 at 12:45 +0200, Navrátil, Ondřej wrote: > as per documentation  > >  The COALESCE function returns the first of its arguments that is not null. > > Null is returned only if all arguments are null. > > This is not exactly true. In fact: > The COALESCE function returns the first