COMMENT ON lock

I wanted to know what lock the COMMENT ON command took and I had to look in the source code, makes sense to me that it should be documented. I've also added it to the list of commands that take a SHARE UPDATE EXCLUSIVE lock. Regards, Nikolaidiff --git i/doc/src/sgml/mvcc.sgml w/doc/src/sgml/m

Re: "actual time" in QUERY PLAN for parallel operation when loops is bigger than 1

in correct? Parallel query is explained in https://www.postgresql.org/docs/14/how-parallel-query-works.html and https://www.postgresql.org/docs/14/parallel-plans.html The docs seem clear to me that as the nodes are executed in parallel then the time execution time is not 140.036*3. The 140.0

Re: ALTER TABLE ... SET DATA TYPE removes statistics

? I prefer the link if there is no hard rule. Regards, Nikolai publickey - nikolai.berkoff@pm.me - 0xD189792D.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature

Re: vacuumdb --analyze-in-stages

‐‐‐ Original Message ‐‐‐ On Tuesday, October 19th, 2021 at 01:02, Euler Taveira wrote: > On Mon, Oct 18, 2021, at 8:53 PM, Alvaro Herrera wrote: > > > On 2021-Oct-18, David G. Johnston wrote: > > > > > On Mon, Oct 18, 2021 at 4:02 PM Alvaro Herrera > > > wrote: > > > > > > Given t

vacuumdb --analyze-in-stages

Running --analyze-in-stages on a database with statistics causes the statistics to become significantly worse before they are improved. This could be made clearer in the documentation.diff --git i/doc/src/sgml/ref/vacuumdb.sgml w/doc/src/sgml/ref/vacuumdb.sgml index 223b986..d76c18e 100644 --- i

ALTER TABLE ... SET DATA TYPE removes statistics

The current documentation does not mention that the column statistics are removed which I can see they are in src/backend/commands/tablecmds.c ATExecAlterColumnType /* * Drop any pg_statistic entry for the column, since it's now wrong type */ RemoveStatistics(Rel

Re: Missing mention of autovacuum_work_mem

> Why not keep it simple with > > "If a table has any indexes, this will happen at least once per vacuum, > > after the heap has been completely scanned. It may happen multiple times per > > vacuum if maintenance_work_mem (or, in the case of autovacuum, > > autovacuum_work_mem) is insuffici

Re: Missing mention of autovacuum_work_mem

The memory is set via the maintenance_work_mem unless it is an autovacuum then autovacuum_work_mem will be used." publickey - nikolai.berkoff@pm.me - 0xD189792D.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature