Make one message just like all its siblings.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/d890fa812dd4620db0d092da1cd7cba01494cd21
Modified Files
--
src/backend/storage/page/bufpage.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
MSVC: Add "use File::Path qw(rmtree)".
My back-patch of commit 10b72deafea5972edcafb9eb3f97154f32ccd340 added
calls to File::Path::rmtree(), but v10 and older had not been importing
that symbol. Back-patch to v10, 9.6 and 9.5.
Branch
--
REL9_5_STABLE
Details
---
https://git.postgresql.o
MSVC: Add "use File::Path qw(rmtree)".
My back-patch of commit 10b72deafea5972edcafb9eb3f97154f32ccd340 added
calls to File::Path::rmtree(), but v10 and older had not been importing
that symbol. Back-patch to v10, 9.6 and 9.5.
Branch
--
REL9_6_STABLE
Details
---
https://git.postgresql.o
MSVC: Add "use File::Path qw(rmtree)".
My back-patch of commit 10b72deafea5972edcafb9eb3f97154f32ccd340 added
calls to File::Path::rmtree(), but v10 and older had not been importing
that symbol. Back-patch to v10, 9.6 and 9.5.
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.o
Fix typo in message
I introduced the typo in source code in the course of 75445c1515ff.
Repair.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/a100974751baec7e13a527bf0c378ce8ef2787b6
Modified Files
--
src/backend/commands/subscriptioncmds.c| 2 +-
In the pg_upgrade test suite, remove and recreate "tmp_check".
This allows "vcregress upgradecheck" to pass twice in immediate
succession, and it's more like how $(prove_check) works. Back-patch to
9.5, where pg_upgrade moved to src/bin.
Discussion: https://postgr.es/m/20190520012436.ga1480...@r
In the pg_upgrade test suite, don't write to src/test/regress.
When this suite runs installcheck, redirect file creations from
src/test/regress to src/bin/pg_upgrade/tmp_check/regress. This closes a
race condition in "make -j check-world". If the pg_upgrade suite wrote
to a given src/test/regres
In the pg_upgrade test suite, remove and recreate "tmp_check".
This allows "vcregress upgradecheck" to pass twice in immediate
succession, and it's more like how $(prove_check) works. Back-patch to
9.5, where pg_upgrade moved to src/bin.
Discussion: https://postgr.es/m/20190520012436.ga1480...@r
In the pg_upgrade test suite, remove and recreate "tmp_check".
This allows "vcregress upgradecheck" to pass twice in immediate
succession, and it's more like how $(prove_check) works. Back-patch to
9.5, where pg_upgrade moved to src/bin.
Discussion: https://postgr.es/m/20190520012436.ga1480...@r
In the pg_upgrade test suite, don't write to src/test/regress.
When this suite runs installcheck, redirect file creations from
src/test/regress to src/bin/pg_upgrade/tmp_check/regress. This closes a
race condition in "make -j check-world". If the pg_upgrade suite wrote
to a given src/test/regres
In the pg_upgrade test suite, don't write to src/test/regress.
When this suite runs installcheck, redirect file creations from
src/test/regress to src/bin/pg_upgrade/tmp_check/regress. This closes a
race condition in "make -j check-world". If the pg_upgrade suite wrote
to a given src/test/regres
In the pg_upgrade test suite, don't write to src/test/regress.
When this suite runs installcheck, redirect file creations from
src/test/regress to src/bin/pg_upgrade/tmp_check/regress. This closes a
race condition in "make -j check-world". If the pg_upgrade suite wrote
to a given src/test/regres
In the pg_upgrade test suite, don't write to src/test/regress.
When this suite runs installcheck, redirect file creations from
src/test/regress to src/bin/pg_upgrade/tmp_check/regress. This closes a
race condition in "make -j check-world". If the pg_upgrade suite wrote
to a given src/test/regres
In the pg_upgrade test suite, remove and recreate "tmp_check".
This allows "vcregress upgradecheck" to pass twice in immediate
succession, and it's more like how $(prove_check) works. Back-patch to
9.5, where pg_upgrade moved to src/bin.
Discussion: https://postgr.es/m/20190520012436.ga1480...@r
In the pg_upgrade test suite, remove and recreate "tmp_check".
This allows "vcregress upgradecheck" to pass twice in immediate
succession, and it's more like how $(prove_check) works. Back-patch to
9.5, where pg_upgrade moved to src/bin.
Discussion: https://postgr.es/m/20190520012436.ga1480...@r
v12 release notes: Correct contributor name.
Mea culpa.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/d5ec46bf224d2ea1b010b2bc10a65e44d4456553
Modified Files
--
doc/src/sgml/release-12.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fix comment
This code block was copied/adapted from other similar places but
somehow the comment placement was changed so that it makes less sense.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/a94fd139df975a006d1697d2a7180d3656222d4d
Modified Files
-
docs: PG 12 relnote wording fix
Reported-by: Gaby Schilders
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/3ceaed106d95e76c7dbfd41f5d83a163fd0d25c8
Modified Files
--
doc/src/sgml/release-12.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fix typos in SQL scripts of pgcrypto
Author: Gurjeet Singh
Discussion:
https://postgr.es/m/cabwtf4u_5kenh93pxzeueszhuossubeoqc6pian8vdflzsq...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/af94ea7406f332567331a9b2525fae4b57c96061
Modified Files
--
19 matches
Mail list logo
