doc: fix trigger inheritance wording
Fix wording from commit 1cf1112990cff432b53a74a0ac9ca897ce8a7688
Reported-by: Robert Haas
Backpatch-through: 10
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/eab30cc6b55dc03589bda13bc76b12d7142d5686
Modified Files
-
doc: fix trigger inheritance wording
Fix wording from commit 1cf1112990cff432b53a74a0ac9ca897ce8a7688
Reported-by: Robert Haas
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/94a2b075779b599c6ee21f04cfafdd68cd84797d
Modified Files
--
doc: clarify major/minor pg_upgrade versions with examples
The previous docs added in PG 10 were not clear enough for someone who
didn't understand the PG 10 version change, so give more specific
examples.
Reported-by: j...@room118solutions.com
Discussion:
https://postgr.es/m/20171218213041.25
doc: clarify major/minor pg_upgrade versions with examples
The previous docs added in PG 10 were not clear enough for someone who
didn't understand the PG 10 version change, so give more specific
examples.
Reported-by: j...@room118solutions.com
Discussion:
https://postgr.es/m/20171218213041.25
doc: clearify trigger behavior for inheritance
The previous wording added in PG 10 wasn't specific enough about the
behavior of statement and row triggers when using inheritance.
Reported-by: i...@thepathcentral.com
Discussion:
https://postgr.es/m/20171129193934.27108.30...@wrigleys.postgresql
doc: clearify trigger behavior for inheritance
The previous wording added in PG 10 wasn't specific enough about the
behavior of statement and row triggers when using inheritance.
Reported-by: i...@thepathcentral.com
Discussion:
https://postgr.es/m/20171129193934.27108.30...@wrigleys.postgresql
doc: in contrib-spi, mention and link to the meaning of SPI
Also remove outdated comment about SPI subtransactions.
Reported-by: greg...@arenius.com
Discussion:
https://postgr.es/m/151726276676.1240.10501743959198501...@wrigleys.postgresql.org
Backpatch-through: 9.3
Branch
--
REL9_4_STAB
doc: in contrib-spi, mention and link to the meaning of SPI
Also remove outdated comment about SPI subtransactions.
Reported-by: greg...@arenius.com
Discussion:
https://postgr.es/m/151726276676.1240.10501743959198501...@wrigleys.postgresql.org
Backpatch-through: 9.3
Branch
--
master
Det
doc: in contrib-spi, mention and link to the meaning of SPI
Also remove outdated comment about SPI subtransactions.
Reported-by: greg...@arenius.com
Discussion:
https://postgr.es/m/151726276676.1240.10501743959198501...@wrigleys.postgresql.org
Backpatch-through: 9.3
Branch
--
REL9_5_STAB
doc: in contrib-spi, mention and link to the meaning of SPI
Also remove outdated comment about SPI subtransactions.
Reported-by: greg...@arenius.com
Discussion:
https://postgr.es/m/151726276676.1240.10501743959198501...@wrigleys.postgresql.org
Backpatch-through: 9.3
Branch
--
REL9_6_STAB
doc: in contrib-spi, mention and link to the meaning of SPI
Also remove outdated comment about SPI subtransactions.
Reported-by: greg...@arenius.com
Discussion:
https://postgr.es/m/151726276676.1240.10501743959198501...@wrigleys.postgresql.org
Backpatch-through: 9.3
Branch
--
REL9_3_STAB
doc: in contrib-spi, mention and link to the meaning of SPI
Also remove outdated comment about SPI subtransactions.
Reported-by: greg...@arenius.com
Discussion:
https://postgr.es/m/151726276676.1240.10501743959198501...@wrigleys.postgresql.org
Backpatch-through: 9.3
Branch
--
REL_10_STAB
Fix typo: colums -> columns.
Along the way, also fix code indentation.
Alexander Lakhin, reviewed by Michael Paquier
Discussion: http://postgr.es/m/45c44aa7-7cfa-7f3b-83fd-d8300677f...@gmail.com
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/a9fd6c321672c1
Fix typo: colums -> columns.
Along the way, also fix code indentation.
Alexander Lakhin, reviewed by Michael Paquier
Discussion: http://postgr.es/m/45c44aa7-7cfa-7f3b-83fd-d8300677f...@gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/22757960bb3b2a6fa331b
doc: Improve pg_upgrade rsync examples to use clusterdir
Commit 9521ce4a7a1125385fb4de9689f345db594c516a from Sep 13, 2017 and
backpatched through 9.5 used rsync examples with datadir. The reporter
has pointed out, and testing has verified, that clusterdir must be used,
so update the docs accordi
doc: Improve pg_upgrade rsync examples to use clusterdir
Commit 9521ce4a7a1125385fb4de9689f345db594c516a from Sep 13, 2017 and
backpatched through 9.5 used rsync examples with datadir. The reporter
has pointed out, and testing has verified, that clusterdir must be used,
so update the docs accordi
doc: Improve pg_upgrade rsync examples to use clusterdir
Commit 9521ce4a7a1125385fb4de9689f345db594c516a from Sep 13, 2017 and
backpatched through 9.5 used rsync examples with datadir. The reporter
has pointed out, and testing has verified, that clusterdir must be used,
so update the docs accordi
doc: Improve pg_upgrade rsync examples to use clusterdir
Commit 9521ce4a7a1125385fb4de9689f345db594c516a from Sep 13, 2017 and
backpatched through 9.5 used rsync examples with datadir. The reporter
has pointed out, and testing has verified, that clusterdir must be used,
so update the docs accordi
pgcrypto's encrypt() supports AES-128, AES-192, and AES-256
Previously, only 128 was mentioned, but the others are also supported.
Thomas Munro, reviewed by Michael Paquier and extended a bit by me.
Discussion:
http://postgr.es/m/CAEepm=1xbbhxyjkofgjnm2qfz-zbvqhgu4aqvtgr+hegy4f...@mail.gmail.co
pgcrypto's encrypt() supports AES-128, AES-192, and AES-256
Previously, only 128 was mentioned, but the others are also supported.
Thomas Munro, reviewed by Michael Paquier and extended a bit by me.
Discussion:
http://postgr.es/m/CAEepm=1xbbhxyjkofgjnm2qfz-zbvqhgu4aqvtgr+hegy4f...@mail.gmail.co
pgcrypto's encrypt() supports AES-128, AES-192, and AES-256
Previously, only 128 was mentioned, but the others are also supported.
Thomas Munro, reviewed by Michael Paquier and extended a bit by me.
Discussion:
http://postgr.es/m/CAEepm=1xbbhxyjkofgjnm2qfz-zbvqhgu4aqvtgr+hegy4f...@mail.gmail.co
pgcrypto's encrypt() supports AES-128, AES-192, and AES-256
Previously, only 128 was mentioned, but the others are also supported.
Thomas Munro, reviewed by Michael Paquier and extended a bit by me.
Discussion:
http://postgr.es/m/CAEepm=1xbbhxyjkofgjnm2qfz-zbvqhgu4aqvtgr+hegy4f...@mail.gmail.co
pgcrypto's encrypt() supports AES-128, AES-192, and AES-256
Previously, only 128 was mentioned, but the others are also supported.
Thomas Munro, reviewed by Michael Paquier and extended a bit by me.
Discussion:
http://postgr.es/m/CAEepm=1xbbhxyjkofgjnm2qfz-zbvqhgu4aqvtgr+hegy4f...@mail.gmail.co
pgcrypto's encrypt() supports AES-128, AES-192, and AES-256
Previously, only 128 was mentioned, but the others are also supported.
Thomas Munro, reviewed by Michael Paquier and extended a bit by me.
Discussion:
http://postgr.es/m/CAEepm=1xbbhxyjkofgjnm2qfz-zbvqhgu4aqvtgr+hegy4f...@mail.gmail.co
doc: mention datadir locations are actually config locations
Technically, pg_upgrade's --old-datadir and --new-datadir are
configuration directories, not necessarily data directories. This is
reflected in the 'postgres' manual page, so do the same for pg_upgrade.
Reported-by: Yves Goergen
Bug:
doc: mention datadir locations are actually config locations
Technically, pg_upgrade's --old-datadir and --new-datadir are
configuration directories, not necessarily data directories. This is
reflected in the 'postgres' manual page, so do the same for pg_upgrade.
Reported-by: Yves Goergen
Bug:
Fix list partition constraints for partition keys of array type.
The old code generated always generated a constraint of the form
col = ANY(ARRAY[val1, val2, ...]), but that's invalid when col is an
array type. Instead, generate col = val when there's only one value,
col = val1 OR col = val2 OR .
Fix list partition constraints for partition keys of array type.
The old code generated always generated a constraint of the form
col = ANY(ARRAY[val1, val2, ...]), but that's invalid when col is an
array type. Instead, generate col = val when there's only one value,
col = val1 OR col = val2 OR .
pg_prewarm: Add missing LWLockRegisterTranche call.
Commit 79ccd7cbd5ca44bee0191d12e9e65abf702899e7, which added automatic
prewarming, neglected this.
Kyotaro Horiguchi, reviewed by me.
Discussion:
http://postgr.es/m/20171215.173219.38055760.horiguchi.kyot...@lab.ntt.co.jp
Branch
--
master
29 matches
Mail list logo
