docs: clarify plpython SD and GD dictionary behavior
Reported-by: Adam Bielański
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.3
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/06d47f6dc
docs: clarify plpython SD and GD dictionary behavior
Reported-by: Adam Bielański
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.3
Branch
--
REL9_3_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/96e578b6c
docs: clarify plpython SD and GD dictionary behavior
Reported-by: Adam Bielański
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.3
Branch
--
REL9_4_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/3c74f7af0
docs: clarify plpython SD and GD dictionary behavior
Reported-by: Adam Bielański
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.3
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/2c852e3e5
docs: clarify plpython SD and GD dictionary behavior
Reported-by: Adam Bielański
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.3
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/9de7ae32c
docs: clarify plpython SD and GD dictionary behavior
Reported-by: Adam Bielański
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.3
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/028f85584
docs: clarify plpython SD and GD dictionary behavior
Reported-by: Adam Bielański
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.3
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/a6ca9c2a1bd0d57e
docs: Clarify pg_ctl initdb option text to match options proto.
The options string appeared in PG 10.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
-
docs: Clarify pg_ctl initdb option text to match options proto.
The options string appeared in PG 10.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 10
Branch
--
master
Details
---
docs: Clarify pg_ctl initdb option text to match options proto.
The options string appeared in PG 10.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 10
Branch
--
REL_11_STABLE
Details
-
Comment fix for rewriteheap.h.
The description of the filename for mapping files did not match the
code.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/e75733d46c8444c0f5c9578bdf576b29039aac1f
Modified Files
--
src/include/access/rewriteheap.h | 6 +++-
Change extension of spilled ReorderBufferChange data to ".tmp".
The previous extension, ".snap", was chosen for historical reasons and
became confusing.
Discussion:
https://postgr.es/m/CAMp0ubd_P8vBGx8=mfdxqjzxha5d_zarw5cckdxj_63+pwr...@mail.gmail.com
Branch
--
master
Details
---
https
Hi,
On August 25, 2018 9:39:12 AM PDT, Jeff Davis wrote:
>Change extension of spilled ReorderBufferChange data to ".tmp".
>
>The previous extension, ".snap", was chosen for historical reasons and
>became confusing.
Not a fan of .tmp, that well just lead to people deleting them while the serve
doc: add doc link for 'applicable_roles'
Reported-by: Ashutosh Sharma
Discussion:
https://postgr.es/m/cae9k0pnhnl6mndluvkk8uszoa_dpzdzfqpam_uaguxbh9hm...@mail.gmail.com
Author: Ashutosh Sharma
Backpatch-through: 9.3
Branch
--
REL9_3_STABLE
Details
---
https://git.postgresql.org/pg/c
doc: add doc link for 'applicable_roles'
Reported-by: Ashutosh Sharma
Discussion:
https://postgr.es/m/cae9k0pnhnl6mndluvkk8uszoa_dpzdzfqpam_uaguxbh9hm...@mail.gmail.com
Author: Ashutosh Sharma
Backpatch-through: 9.3
Branch
--
REL9_4_STABLE
Details
---
https://git.postgresql.org/pg/c
doc: add doc link for 'applicable_roles'
Reported-by: Ashutosh Sharma
Discussion:
https://postgr.es/m/cae9k0pnhnl6mndluvkk8uszoa_dpzdzfqpam_uaguxbh9hm...@mail.gmail.com
Author: Ashutosh Sharma
Backpatch-through: 9.3
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/c
doc: add doc link for 'applicable_roles'
Reported-by: Ashutosh Sharma
Discussion:
https://postgr.es/m/cae9k0pnhnl6mndluvkk8uszoa_dpzdzfqpam_uaguxbh9hm...@mail.gmail.com
Author: Ashutosh Sharma
Backpatch-through: 9.3
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/c
doc: add doc link for 'applicable_roles'
Reported-by: Ashutosh Sharma
Discussion:
https://postgr.es/m/cae9k0pnhnl6mndluvkk8uszoa_dpzdzfqpam_uaguxbh9hm...@mail.gmail.com
Author: Ashutosh Sharma
Backpatch-through: 9.3
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/c
doc: add doc link for 'applicable_roles'
Reported-by: Ashutosh Sharma
Discussion:
https://postgr.es/m/cae9k0pnhnl6mndluvkk8uszoa_dpzdzfqpam_uaguxbh9hm...@mail.gmail.com
Author: Ashutosh Sharma
Backpatch-through: 9.3
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdi
doc: add doc link for 'applicable_roles'
Reported-by: Ashutosh Sharma
Discussion:
https://postgr.es/m/cae9k0pnhnl6mndluvkk8uszoa_dpzdzfqpam_uaguxbh9hm...@mail.gmail.com
Author: Ashutosh Sharma
Backpatch-through: 9.3
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.org/pg/c
Andres Freund writes:
> On August 25, 2018 9:39:12 AM PDT, Jeff Davis wrote:
>> Change extension of spilled ReorderBufferChange data to ".tmp".
>> The previous extension, ".snap", was chosen for historical reasons and
>> became confusing.
> Not a fan of .tmp, that well just lead to people deleti
doc: "Latest checkpoint location" will not match in pg_upgrade
Mention that "Latest checkpoint location" will not match in pg_upgrade
if the standby server is still running during the upgrade, which is
possible. "Match" text first appeared in PG 9.5.
Reported-by: Paul Bonaud
Discussion:
https
doc: "Latest checkpoint location" will not match in pg_upgrade
Mention that "Latest checkpoint location" will not match in pg_upgrade
if the standby server is still running during the upgrade, which is
possible. "Match" text first appeared in PG 9.5.
Reported-by: Paul Bonaud
Discussion:
https
doc: "Latest checkpoint location" will not match in pg_upgrade
Mention that "Latest checkpoint location" will not match in pg_upgrade
if the standby server is still running during the upgrade, which is
possible. "Match" text first appeared in PG 9.5.
Reported-by: Paul Bonaud
Discussion:
https
doc: "Latest checkpoint location" will not match in pg_upgrade
Mention that "Latest checkpoint location" will not match in pg_upgrade
if the standby server is still running during the upgrade, which is
possible. "Match" text first appeared in PG 9.5.
Reported-by: Paul Bonaud
Discussion:
https
doc: "Latest checkpoint location" will not match in pg_upgrade
Mention that "Latest checkpoint location" will not match in pg_upgrade
if the standby server is still running during the upgrade, which is
possible. "Match" text first appeared in PG 9.5.
Reported-by: Paul Bonaud
Discussion:
https
doc: correct syntax of pgtrgm examples in older releases
Reported-by: Liudmila Mantrova
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6 and 10 only
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/
doc: correct syntax of pgtrgm examples in older releases
Reported-by: Liudmila Mantrova
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6 and 10 only
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/
Reconsider new file extension in commit 91f26d5f.
Andres and Tom objected to the choice of the ".tmp"
extension. Changing to Andres's suggestion of ".spill".
Discussion:
https://postgr.es/m/88092095-3348-49D8-8746-EB574B1D30EA%40anarazel.de
Branch
--
master
Details
---
https://git.post
29 matches
Mail list logo
