Re: MERGE examples not clear

On Wed, Sep 27, 2023 at 07:42:42PM -0400, Bruce Momjian wrote: > On Tue, Feb 21, 2023 at 08:56:50AM -0700, David G. Johnston wrote: > > On Tue, Feb 21, 2023 at 8:35 AM PG Doc comments form > > > > wrote: > > > > The following documentation comment has been logged on the website: > > > >

Re: incorrect (incomplete) description for "alter domain"

On Wed, Oct 16, 2024 at 05:11:54PM -0400, Bruce Momjian wrote: > > Actually, there *is* a bug in the description, because experimentation > > shows that CREATE DOMAIN accepts NULL in this syntax (as advertised) > > but ALTER DOMAIN does not. We could alternatively decide that that's > > a code bug

Re: Documentation of .pgpass for Unix is incomplete

Thanks, Bruce! > Am 01.11.2024 um 18:32 schrieb Bruce Momjian : > > On Tue, Aug 20, 2024 at 09:24:43AM +0200, Marc Balmer wrote: >> >>> Well, it is more complicated than checking just HOME because it calls >>> getpwuid_r() if HOME is not set: >>> >>> >>> https://doxygen.postgresql.org/fe-

Re: Connection Info

On Wed, Oct 16, 2024 at 09:36:00PM -0400, Bruce Momjian wrote: > On Mon, May 6, 2024 at 04:15:24PM +0200, Laurenz Albe wrote: > > On Sun, 2024-05-05 at 20:25 +, PG Doc comments form wrote: > > > On this page: > > > https://www.postgresql.org/docs/14/server-start.html#CLIENT-CONNECTION-PROBLEMS

Re: Documentation of .pgpass for Unix is incomplete

On Tue, Aug 20, 2024 at 09:24:43AM +0200, Marc Balmer wrote: > > > Well, it is more complicated than checking just HOME because it calls > > getpwuid_r() if HOME is not set: > > > > > > https://doxygen.postgresql.org/fe-connect_8c.html#a3f49cbb20595c1765bd0db5ff434c9c3 > > > > Is it worth g

Re: PostgreSQL limits

On Fri, Nov 1, 2024 at 09:14:20AM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/limits.html > Description: > > I think it can be useful to add the maximum SQL statement length that > PostgreSQ

Re: fir for row level security

On Fri, Nov 1, 2024 at 11:04:53AM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/ddl-rowsecurity.html > Description: > > Cite > When multiple policies apply to a given query, they are combined

Re: Add mention to related system catalog functions on Tablespaces documentation pages.

On Mon, Oct 14, 2024 at 07:21:32PM -0400, Bruce Momjian wrote: > On Mon, Oct 14, 2024 at 07:15:50PM -0400, Bruce Momjian wrote: > > On Wed, Sep 11, 2024 at 11:26:50PM +, PG Doc comments form wrote: > > Yes, very good points. I have developed the attached patch which I > > think achieves the go

Re: Mistake in statement example

On Wed, Sep 27, 2023 at 07:23:09PM -0400, Bruce Momjian wrote: > On Wed, Mar 1, 2023 at 09:45:00AM -0700, David G. Johnston wrote: > > That may be, but the descriptive text and point of the example (which isn't > > atomicity, but concurrency) doesn't even require the second update command > > to

RE: Tip box on Adding a Column

On 2024-11-01 09:25:24, David Rowley wrote: > We have the ability to store immutable defaults in the catalogue tables and > "fill in the blanks" from there for any tuples that don't have the new > column. Since we only can store 1 value per column, it must be a constant, > i.e. the same for all r

Re: Tip box on Adding a Column

On Fri, 1 Nov 2024 at 22:06, Marcelo Fernandes wrote: > - > https://www.postgresql.org/docs/current/ddl-alter.html#DDL-ALTER-ADDING-A-COLUMN > > That says: > > > From PostgreSQL 11, adding a column with a constant default value no longer > > means that each row of the table needs to be updated wh

Tip box on Adding a Column

Hi folks, We have this Tip box under the "Adding a Column" header here: - https://www.postgresql.org/docs/current/ddl-alter.html#DDL-ALTER-ADDING-A-COLUMN That says: > From PostgreSQL 11, adding a column with a constant default value no longer > means that each row of the table needs to be upd

fir for row level security

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/ddl-rowsecurity.html Description: Cite When multiple policies apply to a given query, they are combined using either OR (for permissive policies, which are the default) or using AND (for r

PostgreSQL limits

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/limits.html Description: I think it can be useful to add the maximum SQL statement length that PostgreSQL can handle in the Appendix K. PostgreSQL Limits. If I'm not wrong it is 2147483648