Re: DROP TRIGGER lock

On Fri, Jun 7, 2024, at 12:06 PM, Dull Bananas wrote: > On these pages, it should be mentioned that DROP TRIGGER acquires an ACCESS > EXCLUSIVE lock: > > https://www.postgresql.org/docs/16/explicit-locking.html#LOCKING-TABLES > > h

Suggestion about tcp_keepalives_idle parameter in the document

there is the following description in the https://www.postgresql.org/docs/current/runtime-config-connection.html： A value of 0 (the default) selects the operating system's default.-but there is no description about“ the operating system's default value in the linux is tcp_keepalive_ti

Re: CLUSTER details

On Fri, Jun 7, 2024, 10:57 Bernd Eckenfels wrote: > > Is the following correct (I.e. it does not preserv free pages) and can > be added? > You are hung up on the idea of free pages when this operation makes them irrelevant. Complete new files are written, populated to the extent of fill factor,

DROP TRIGGER lock

On these pages, it should be mentioned that DROP TRIGGER acquires an ACCESS EXCLUSIVE lock: https://www.postgresql.org/docs/16/explicit-locking.html#LOCKING-TABLES https://www.postgresql.org/docs/16/sql-droptrigger.html

Re: I get ERROR: column "table_name" does not exist

On 2024-06-07 14:24 +0200, Florian Koch wrote: > I made a gist with the error. > https://gist.github.com/floratmin/a4b404f0fd66b03a0428c07686b71410 The problem is the semicolon after PG_DATATYPE_NAME, causing the TABLE_NAME line to be a separate statement: >exception_datatype := PG_DATATYPE_N

Re: CLUSTER details

On Thursday, June 6, 2024, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/16/sql-cluster.html > Description: > > The cloister command should describe how or deals with free pages (I.e. are > released) and

Re: Ambiguous description on new columns

Yes, this change is clear to me that the "columns added" applies to the table on the publisher. Regards, Koen De Groote On Tue, Jun 4, 2024 at 7:57 AM Amit Kapila wrote: > On Fri, May 31, 2024 at 10:54 PM Peter Smith > wrote: > > > > On Wed, May 29, 2024 at 8:04 PM vignesh C wrote: > > > > >

Re: Ambiguous description on new columns

On Tue, Jun 4, 2024 at 11:26 AM Amit Kapila wrote: > > > > > IIUC you're saying my v1 patch *content* and rendering is OK, but you > > only wanted the SGML text to have better wrapping for < 80 chars > > lines. So I have attached a patch v2 with improved wrapping. If you > > meant something differ

Re: I get ERROR: column "table_name" does not exist

This is the working example, when I replace any of e.g. 'PG_EXCEPTION_HINT' with 'TABLE_NAME'. Then the function throws. I am using postgres 16.1. On Wed, Jun 5, 2024 at 6:32 PM Erik Wienhold wrote: > > On 2024-06-04 21:50 +0200, PG Doc comments form wrote: > > When using GET STACKED DIAGNOSTICS

Re: CLUSTER details

I just noticed, it does describe that it takes an exclusive access lock, so that part is covered. (Maybe add „This is not an „ONLINE“ operation“ as this use a more common terminology?) Thanks for your workBernd  Von: PG Doc comments form Gesendet: Freitag, Juni 7, 2024 5:

CLUSTER details

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/16/sql-cluster.html Description: The cloister command should describe how or deals with free pages (I.e. are released) and what it’s lock model is (i.e. that it is (not yet?) an online operat