Re: pgsql: walreceiver uses a temporary replication slot by default

2020-02-12 Thread Michael Paquier
On Wed, Feb 12, 2020 at 06:11:06PM +0900, Fujii Masao wrote: > On 2020/02/12 7:53, Jehan-Guillaume de Rorthais wrote: >> In my humble opinion, I prefer the previous behavior, streaming without >> temporary slot, for one reason: primary availability. > > +1 > >> With temp slot created by default, i

pgsql: Doc: Restructure B-Tree support routine docs.

2020-02-12 Thread Peter Geoghegan
Doc: Restructure B-Tree support routine docs. Use a top-level "variablelist", with one item per B-Tree support function. This structure matches the structure used by various "Extensibility" sections in other documentation chapters for other index access methods. An explicit list makes it much cl

pgsql: Remove long-dead comments.

2020-02-12 Thread Tom Lane
Remove long-dead comments. These should've been dropped by a8bb8eb58, but evidently were missed. Not important enough to back-patch. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/0973f5602c349ad99fae6f57cdcc26754a03ba83 Modified Files -- src/backend/

pgsql: Doc: fix old oversights in GRANT/REVOKE documentation.

2020-02-12 Thread Tom Lane
Doc: fix old oversights in GRANT/REVOKE documentation. The GRANTED BY clause in GRANT/REVOKE ROLE has been there since 2005 but was never documented. I'm not sure now whether that was just an oversight or was intentional (given the limited capability of the option). But seeing that pg_dumpall do

pgsql: Doc: fix old oversights in GRANT/REVOKE documentation.

2020-02-12 Thread Tom Lane
Doc: fix old oversights in GRANT/REVOKE documentation. The GRANTED BY clause in GRANT/REVOKE ROLE has been there since 2005 but was never documented. I'm not sure now whether that was just an oversight or was intentional (given the limited capability of the option). But seeing that pg_dumpall do

pgsql: Doc: fix old oversights in GRANT/REVOKE documentation.

2020-02-12 Thread Tom Lane
Doc: fix old oversights in GRANT/REVOKE documentation. The GRANTED BY clause in GRANT/REVOKE ROLE has been there since 2005 but was never documented. I'm not sure now whether that was just an oversight or was intentional (given the limited capability of the option). But seeing that pg_dumpall do

pgsql: Doc: fix old oversights in GRANT/REVOKE documentation.

2020-02-12 Thread Tom Lane
Doc: fix old oversights in GRANT/REVOKE documentation. The GRANTED BY clause in GRANT/REVOKE ROLE has been there since 2005 but was never documented. I'm not sure now whether that was just an oversight or was intentional (given the limited capability of the option). But seeing that pg_dumpall do

pgsql: Doc: fix old oversights in GRANT/REVOKE documentation.

2020-02-12 Thread Tom Lane
Doc: fix old oversights in GRANT/REVOKE documentation. The GRANTED BY clause in GRANT/REVOKE ROLE has been there since 2005 but was never documented. I'm not sure now whether that was just an oversight or was intentional (given the limited capability of the option). But seeing that pg_dumpall do

pgsql: Doc: fix old oversights in GRANT/REVOKE documentation.

2020-02-12 Thread Tom Lane
Doc: fix old oversights in GRANT/REVOKE documentation. The GRANTED BY clause in GRANT/REVOKE ROLE has been there since 2005 but was never documented. I'm not sure now whether that was just an oversight or was intentional (given the limited capability of the option). But seeing that pg_dumpall do

Re: pgsql: walreceiver uses a temporary replication slot by default

2020-02-12 Thread Fujii Masao
On 2020/02/12 7:53, Jehan-Guillaume de Rorthais wrote: Hello, On Mon, 10 Feb 2020 16:37:53 +0100 Peter Eisentraut wrote: On 2020-01-23 21:49, Robert Haas wrote: On Tue, Jan 14, 2020 at 8:57 AM Peter Eisentraut wrote: walreceiver uses a temporary replication slot by default If no perman