pgsql: Fix non-specific error message.

2022-08-11 Thread Robert Haas
Fix non-specific error message. "something has gone wrong" is not helpful. Make this elog() consistent with the other one in the same function. Discussion: http://postgr.es/m/ca+tgmoa_az2juwsa_noiqoqnxbawdr+t3bhjsygzi6+wqdb...@mail.gmail.com Branch -- master Details ---

pgsql: Tag refs/tags/REL_12_12 was created

2022-08-11 Thread noreply
Tag refs/tags/REL_12_12 was created.

pgsql: Tag refs/tags/REL_14_5 was created

2022-08-11 Thread noreply
Tag refs/tags/REL_14_5 was created.

pgsql: Tag refs/tags/REL_11_17 was created

2022-08-11 Thread noreply
Tag refs/tags/REL_11_17 was created.

pgsql: Tag refs/tags/REL_13_8 was created

2022-08-11 Thread noreply
Tag refs/tags/REL_13_8 was created.

pgsql: Tag refs/tags/REL_15_BETA3 was created

2022-08-11 Thread noreply
Tag refs/tags/REL_15_BETA3 was created.

pgsql: Tag refs/tags/REL_10_22 was created

2022-08-11 Thread noreply
Tag refs/tags/REL_10_22 was created.

pgsql: Stabilize output of new regression test.

2022-08-11 Thread Tom Lane
Stabilize output of new regression test. Per buildfarm, the output order of \dx+ isn't consistent across locales. Apply NO_LOCALE to force C locale. There might be a more localized way, but I'm not seeing it offhand, and anyway there is nothing in this test module that particularly cares about

pgsql: Stabilize output of new regression test.

2022-08-11 Thread Tom Lane
Stabilize output of new regression test. Per buildfarm, the output order of \dx+ isn't consistent across locales. Apply NO_LOCALE to force C locale. There might be a more localized way, but I'm not seeing it offhand, and anyway there is nothing in this test module that particularly cares about

pgsql: Stabilize output of new regression test.

2022-08-11 Thread Tom Lane
Stabilize output of new regression test. Per buildfarm, the output order of \dx+ isn't consistent across locales. Apply NO_LOCALE to force C locale. There might be a more localized way, but I'm not seeing it offhand, and anyway there is nothing in this test module that particularly cares about

pgsql: Stabilize output of new regression test.

2022-08-11 Thread Tom Lane
Stabilize output of new regression test. Per buildfarm, the output order of \dx+ isn't consistent across locales. Apply NO_LOCALE to force C locale. There might be a more localized way, but I'm not seeing it offhand, and anyway there is nothing in this test module that particularly cares about

pgsql: Stabilize output of new regression test.

2022-08-11 Thread Tom Lane
Stabilize output of new regression test. Per buildfarm, the output order of \dx+ isn't consistent across locales. Apply NO_LOCALE to force C locale. There might be a more localized way, but I'm not seeing it offhand, and anyway there is nothing in this test module that particularly cares about

pgsql: Stabilize output of new regression test.

2022-08-11 Thread Tom Lane
Stabilize output of new regression test. Per buildfarm, the output order of \dx+ isn't consistent across locales. Apply NO_LOCALE to force C locale. There might be a more localized way, but I'm not seeing it offhand, and anyway there is nothing in this test module that particularly cares about

pgsql: Stabilize output of new regression test.

2022-08-11 Thread Tom Lane
Stabilize output of new regression test. Per buildfarm, the output order of \dx+ isn't consistent across locales. Apply NO_LOCALE to force C locale. There might be a more localized way, but I'm not seeing it offhand, and anyway there is nothing in this test module that particularly cares about

pgsql: Last-minute updates for release notes.

2022-08-11 Thread Tom Lane
Last-minute updates for release notes. Security: CVE-2022-2625 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/30523c0ca1186476674d2874754cf218627e9de2 Modified Files -- doc/src/sgml/release-13.sgml | 35 +++ 1

pgsql: Last-minute updates for release notes.

2022-08-11 Thread Tom Lane
Last-minute updates for release notes. Security: CVE-2022-2625 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/ea2917ca905b7a669cc9d90c3b0e4539667a15a4 Modified Files -- doc/src/sgml/release-14.sgml | 35 +++ 1

pgsql: Last-minute updates for release notes.

2022-08-11 Thread Tom Lane
Last-minute updates for release notes. Security: CVE-2022-2625 Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/197671018875d278db7075f604eca02b42a33c3e Modified Files -- doc/src/sgml/release-11.sgml | 35 +++ 1

pgsql: Last-minute updates for release notes.

2022-08-11 Thread Tom Lane
Last-minute updates for release notes. Security: CVE-2022-2625 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/cd1aef2972ed0b4aafc18c58495cc7e62eebc4c8 Modified Files -- doc/src/sgml/release-10.sgml | 35 +++ 1

pgsql: Last-minute updates for release notes.

2022-08-11 Thread Tom Lane
Last-minute updates for release notes. Security: CVE-2022-2625 Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a2398bf8b6413338faeb75cbb40a347be0741972 Modified Files -- doc/src/sgml/release-12.sgml | 35 +++ 1

pgsql: In extensions, don't replace objects not belonging to the extens

2022-08-11 Thread Tom Lane
In extensions, don't replace objects not belonging to the extension. Previously, if an extension script did CREATE OR REPLACE and there was an existing object not belonging to the extension, it would overwrite the object and adopt it into the extension. This is problematic, first because the

pgsql: In extensions, don't replace objects not belonging to the extens

2022-08-11 Thread Tom Lane
In extensions, don't replace objects not belonging to the extension. Previously, if an extension script did CREATE OR REPLACE and there was an existing object not belonging to the extension, it would overwrite the object and adopt it into the extension. This is problematic, first because the

pgsql: In extensions, don't replace objects not belonging to the extens

2022-08-11 Thread Tom Lane
In extensions, don't replace objects not belonging to the extension. Previously, if an extension script did CREATE OR REPLACE and there was an existing object not belonging to the extension, it would overwrite the object and adopt it into the extension. This is problematic, first because the

pgsql: In extensions, don't replace objects not belonging to the extens

2022-08-11 Thread Tom Lane
In extensions, don't replace objects not belonging to the extension. Previously, if an extension script did CREATE OR REPLACE and there was an existing object not belonging to the extension, it would overwrite the object and adopt it into the extension. This is problematic, first because the

pgsql: In extensions, don't replace objects not belonging to the extens

2022-08-11 Thread Tom Lane
In extensions, don't replace objects not belonging to the extension. Previously, if an extension script did CREATE OR REPLACE and there was an existing object not belonging to the extension, it would overwrite the object and adopt it into the extension. This is problematic, first because the

pgsql: In extensions, don't replace objects not belonging to the extens

2022-08-11 Thread Tom Lane
In extensions, don't replace objects not belonging to the extension. Previously, if an extension script did CREATE OR REPLACE and there was an existing object not belonging to the extension, it would overwrite the object and adopt it into the extension. This is problematic, first because the

pgsql: In extensions, don't replace objects not belonging to the extens

2022-08-11 Thread Tom Lane
In extensions, don't replace objects not belonging to the extension. Previously, if an extension script did CREATE OR REPLACE and there was an existing object not belonging to the extension, it would overwrite the object and adopt it into the extension. This is problematic, first because the

pgsql: struct PQWalReceiverFunctions: use designated initializers

2022-08-11 Thread Alvaro Herrera
struct PQWalReceiverFunctions: use designated initializers We now require that compilers support this, and it makes the code easier to trace, so change it. I'm fixated on this particular struct because I've had to navigate around it a number of times, but there are others elsewhere that could

pgsql: Add missing space in _outA_Const() output

2022-08-11 Thread Peter Eisentraut
Add missing space in _outA_Const() output Mistake introduced by 639a86e36aaecb84faaf941dcd0b183ba0aba9e9. Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/eeb1671b1195341df156c9b11a3c676000e1bcd1 Modified Files -- src/backend/nodes/outfuncs.c | 2

pgsql: Add missing space in _outA_Const() output

2022-08-11 Thread Peter Eisentraut
Add missing space in _outA_Const() output Mistake introduced by 639a86e36aaecb84faaf941dcd0b183ba0aba9e9. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4e6dcbb6ae77d9f6f20072d19e433cab8329ea9b Modified Files -- src/backend/nodes/outfuncs.c | 2 +- 1