Re: pg_dump shared locks documentation

2022-03-15 Thread Florin Irion
On 15/03/22 16:55, Tom Lane wrote: > Alvaro Herrera writes: >> This might be a bit excessive to have in the main text. What about >> adding a footnote to point out the exact lock level that is meant, with >> a link to the server doc page that explains each lock level? > > I dunno how well wil

"Restore" vs. "Reload"

2022-03-15 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/14/backup-dump.html Description: Hello, As far as I can see, the terms "Reload" and "Restore" are used interchangeably. To make the page as easy digestable for the reader as possible, it´s ad

Re: pg_dump shared locks documentation

2022-03-15 Thread Tom Lane
Alvaro Herrera writes: > This might be a bit excessive to have in the main text. What about > adding a footnote to point out the exact lock level that is meant, with > a link to the server doc page that explains each lock level? I dunno how well will render in man-page format. How about just in

Re: pg_dump shared locks documentation

2022-03-15 Thread Alvaro Herrera
On 2022-Mar-15, Florin Irion wrote: > In the `pg_dump` documentation we talk about "shared locks", but IIUC, > we actually take `AccessShareLock`s. This might be misunderstood with > the `ShareLock`. This might be a bit excessive to have in the main text. What about adding a footnote to point o

pg_dump shared locks documentation

2022-03-15 Thread Florin Irion
Hi, In the `pg_dump` documentation we talk about "shared locks", but IIUC, we actually take `AccessShareLock`s. This might be misunderstood with the `ShareLock`. There are 5 occurrences. 4 in `--jobs=njobs` and 1 in `--lock-wait-timeout=timeout` sections. Cheers, Florin IrionFrom 63adb1d3