doc: add example of using pg_dump with GNU split and gzip
This is only possible with GNU split, not other versions like BSD split.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
doc: add example of using pg_dump with GNU split and gzip
This is only possible with GNU split, not other versions like BSD split.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
doc: add example of using pg_dump with GNU split and gzip
This is only possible with GNU split, not other versions like BSD split.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
doc: add example of using pg_dump with GNU split and gzip
This is only possible with GNU split, not other versions like BSD split.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
doc: add example of using pg_dump with GNU split and gzip
This is only possible with GNU split, not other versions like BSD split.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
doc: add example of using pg_dump with GNU split and gzip
This is only possible with GNU split, not other versions like BSD split.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
doc: add example of using pg_dump with GNU split and gzip
This is only possible with GNU split, not other versions like BSD split.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
doc: mention inheritance's tableoid can be used in partitioning
Previously tableoid was not mentioned in the partition doc section. We
only had a link to the "all the normal rules" of inheritance section.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/162627031219.693.
doc: mention inheritance's tableoid can be used in partitioning
Previously tableoid was not mentioned in the partition doc section. We
only had a link to the "all the normal rules" of inheritance section.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/162627031219.693.
doc: mention inheritance's tableoid can be used in partitioning
Previously tableoid was not mentioned in the partition doc section. We
only had a link to the "all the normal rules" of inheritance section.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/162627031219.693.
doc: mention inheritance's tableoid can be used in partitioning
Previously tableoid was not mentioned in the partition doc section. We
only had a link to the "all the normal rules" of inheritance section.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/162627031219.693.
doc: mention inheritance's tableoid can be used in partitioning
Previously tableoid was not mentioned in the partition doc section. We
only had a link to the "all the normal rules" of inheritance section.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/162627031219.693.
doc: mention inheritance's tableoid can be used in partitioning
Previously tableoid was not mentioned in the partition doc section. We
only had a link to the "all the normal rules" of inheritance section.
Reported-by: [email protected]
Discussion:
https://postgr.es/m/162627031219.693.
pg_upgrade: improve docs about extension upgrades
The previous wording was unclear about the steps needed to upgrade
extensions, and how to update them after pg_upgrade.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
pg_upgrade: improve docs about extension upgrades
The previous wording was unclear about the steps needed to upgrade
extensions, and how to update them after pg_upgrade.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
pg_upgrade: improve docs about extension upgrades
The previous wording was unclear about the steps needed to upgrade
extensions, and how to update them after pg_upgrade.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
pg_upgrade: improve docs about extension upgrades
The previous wording was unclear about the steps needed to upgrade
extensions, and how to update them after pg_upgrade.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
pg_upgrade: improve docs about extension upgrades
The previous wording was unclear about the steps needed to upgrade
extensions, and how to update them after pg_upgrade.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
pg_upgrade: improve docs about extension upgrades
The previous wording was unclear about the steps needed to upgrade
extensions, and how to update them after pg_upgrade.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
pg_upgrade: improve docs about extension upgrades
The previous wording was unclear about the steps needed to upgrade
extensions, and how to update them after pg_upgrade.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
pg_upgrade: warn about extensions that need updating
Also create a script that can be run to update them.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
Backpatch-through: 9.6
Branch
--
REL9_6_STABLE
Details
--
pg_upgrade: warn about extensions that need updating
Also create a script that can be run to update them.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
Backpatch-through: 9.6
Branch
--
REL_14_STABLE
Details
--
pg_upgrade: warn about extensions that need updating
Also create a script that can be run to update them.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
Backpatch-through: 9.6
Branch
--
REL_10_STABLE
Details
--
pg_upgrade: warn about extensions that need updating
Also create a script that can be run to update them.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
Backpatch-through: 9.6
Branch
--
REL_11_STABLE
Details
--
pg_upgrade: warn about extensions that need updating
Also create a script that can be run to update them.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
Backpatch-through: 9.6
Branch
--
REL_13_STABLE
Details
--
pg_upgrade: warn about extensions that need updating
Also create a script that can be run to update them.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
Backpatch-through: 9.6
Branch
--
REL_12_STABLE
Details
--
pg_upgrade: warn about extensions that need updating
Also create a script that can be run to update them.
Reported-by: Dave Cramer
Discussion:
https://postgr.es/m/CADK3HHKawwbOcGwMGnDuAf3-U8YfvTcS8jqDv3UM=niijs3...@mail.gmail.com
Backpatch-through: 9.6
Branch
--
master
Details
---
h
interval: round values when spilling to months
Previously spilled units greater than months were truncated to months.
Also document the spill behavior.
Reported-by: Bryn Llewelly
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: master
Branc
doc: interval spill method for units greater than months
Units are _truncated_ to months, but only in back branches since the
recent commit.
Reported-by: Bryn Llewellyn
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6 to 14
Branch
-
doc: interval spill method for units greater than months
Units are _truncated_ to months, but only in back branches since the
recent commit.
Reported-by: Bryn Llewellyn
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6 to 14
Branch
-
doc: interval spill method for units greater than months
Units are _truncated_ to months, but only in back branches since the
recent commit.
Reported-by: Bryn Llewellyn
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6 to 14
Branch
-
doc: interval spill method for units greater than months
Units are _truncated_ to months, but only in back branches since the
recent commit.
Reported-by: Bryn Llewellyn
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6 to 14
Branch
-
doc: interval spill method for units greater than months
Units are _truncated_ to months, but only in back branches since the
recent commit.
Reported-by: Bryn Llewellyn
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6 to 14
Branch
-
doc: interval spill method for units greater than months
Units are _truncated_ to months, but only in back branches since the
recent commit.
Reported-by: Bryn Llewellyn
Discussion:
https://postgr.es/m/[email protected]
Backpatch-through: 9.6 to 14
Branch
-
C comment: correct heading of extension query
Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/fcdc461f5c4dd6c970ab7c3b155dbfbd72ecdd2c
M
C comment: correct heading of extension query
Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/9e51cc87fd0ac46b183cb7302a6751d52d3f159a
Modified
C comment: correct heading of extension query
Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/165506217df417c7ca11770599e64d5e93a96fb6
M
C comment: correct heading of extension query
Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/3ab496ab8b144c20e9b03c5fc908cf973e6593cd
M
C comment: correct heading of extension query
Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/3a0ba31a32f2def545399549c2ace6951f98e47c
M
C comment: correct heading of extension query
Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/47a573d9113e18864dcb637b72ee3ac1a9ec6b5e
M
C comment: correct heading of extension query
Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 9.6
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/554a7648ee48f81e3c2e7e7449730ca0e31345f9
M
Add assorted new regexp_xxx SQL functions.
This patch adds new functions regexp_count(), regexp_instr(),
regexp_like(), and regexp_substr(), and extends regexp_replace()
with some new optional arguments. All these functions follow
the definitions used in Oracle, although there are small differenc
Add prepare API support for streaming transactions in logical replication.
Commit a8fd13cab0 added support for prepared transactions to built-in
logical replication via a new option "two_phase" for a subscription. The
"two_phase" option was not allowed with the existing streaming option.
This com
Make vacuum_index_cleanup reloption RELOPT_TYPE_ENUM.
Oversight in commit 3499df0d, which generalized the reloption as a way
of giving users a way to consistently avoid VACUUM's index bypass
optimization.
Per off-list report from Nikolay Shaplov.
Backpatch: 14-, where index cleanup reloption was
Make vacuum_index_cleanup reloption RELOPT_TYPE_ENUM.
Oversight in commit 3499df0d, which generalized the reloption as a way
of giving users a way to consistently avoid VACUUM's index bypass
optimization.
Per off-list report from Nikolay Shaplov.
Backpatch: 14-, where index cleanup reloption was
45 matches
Mail list logo
