pgsql: In INSERT/UPDATE, use the table's real tuple descriptor as targe

In INSERT/UPDATE, use the table's real tuple descriptor as target. This back-patches commit 20d3fe900 into the v12 and v13 branches. At the time I thought that commit was not fixing any observable bug, but Bertrand Drouvot showed otherwise: adding a dropped column to the previously-considered scen

pgsql: In INSERT/UPDATE, use the table's real tuple descriptor as targe

In INSERT/UPDATE, use the table's real tuple descriptor as target. This back-patches commit 20d3fe900 into the v12 and v13 branches. At the time I thought that commit was not fixing any observable bug, but Bertrand Drouvot showed otherwise: adding a dropped column to the previously-considered scen

pgsql: In INSERT/UPDATE, use the table's real tuple descriptor as targe

In INSERT/UPDATE, use the table's real tuple descriptor as target. This back-patches commit 20d3fe900 into the v12 and v13 branches. At the time I thought that commit was not fixing any observable bug, but Bertrand Drouvot showed otherwise: adding a dropped column to the previously-considered scen

pgsql: Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24.

Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24. Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a39e23b8c8d7ae0744619a5e7a14bcc907b696f9 Modified Files -- doc/src/sgml/release-9.6.sgml | 843 ++ 1

pgsql: Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24.

Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24. Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/213774a45b9259ea797cd6b5e1e9a74bd7d12d28 Modified Files -- doc/src/sgml/release-13.sgml | 490 ++- 1

pgsql: Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24.

Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24. Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/cd3c6e50b958f66285a4ea58eb456ca26750e65d Modified Files -- doc/src/sgml/release-12.sgml | 1226 ++ 1

pgsql: Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24.

Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24. Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/4ef7b6450702675d4a01b11dd27e39eea3cea545 Modified Files -- doc/src/sgml/release-10.sgml | 913 +++ 1

pgsql: Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24.

Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24. Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/252ee95ae8e7b6fae272696d50f8c15bc0b9b776 Modified Files -- doc/src/sgml/release-11.sgml | 1021 ++ 1

pgsql: Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24.

Release notes for 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24. Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/35c6838e28489d8e8140219b06fc8a58f75d0b1a Modified Files -- doc/src/sgml/release-9.5.sgml | 804 ++ 1

pgsql: Doc: suppress PDF build warning in 9.6 branch.

Doc: suppress PDF build warning in 9.6 branch. Fractional colwidths seem not to work in the openjade toolchain. Since we have no colwidth specs anywhere else in pre-v10 branches, let's just drop the ones introduced by commits ee59f669b/35b12948a. Branch -- REL9_6_STABLE Details --- https

Re: pgsql: Skip empty transaction stream in test_decoding.

Hi Amit, On Fri, Sep 11, 2020 at 04:43:59AM +, Amit Kapila wrote: > Skip empty transaction stream in test_decoding. > > We were decoding empty transactions via streaming APIs added in commit > 45fdc9738b even when the user used the option 'skip-empty-xacts'. The APIs > makes no effort to skip

Re: pgsql: Skip empty transaction stream in test_decoding.

On Mon, Nov 9, 2020 at 7:11 AM Michael Paquier wrote: > > Hi Amit, > > On Fri, Sep 11, 2020 at 04:43:59AM +, Amit Kapila wrote: > > Skip empty transaction stream in test_decoding. > > > > We were decoding empty transactions via streaming APIs added in commit > > 45fdc9738b even when the user u

pgsql: Fix parsePGArray() error checking in pg_dump.

Fix parsePGArray() error checking in pg_dump. Coverity complained about a defect in commit 257836a7: Calling "parsePGArray" without checking return value (as is done elsewhere 11 out of 13 times). Fix, and also check for empty strings explicitly (NULL as represented by PQgetvalue()). That w

Re: pgsql: Skip empty transaction stream in test_decoding.

On Mon, Nov 9, 2020 at 8:40 AM Amit Kapila wrote: > > On Mon, Nov 9, 2020 at 7:11 AM Michael Paquier wrote: > > > > /home/pgbfarm/buildroot/HEAD/pgsql.build/contrib/test_decoding/output_iso/results/concurrent_stream.out > > 2020-11-08 12:31:10 -0700 > > @@ -13,7 +13,6 @@ > > opening a streamed b

Re: pgsql: Skip empty transaction stream in test_decoding.

On Mon, Nov 9, 2020 at 10:13 AM Amit Kapila wrote: > > On Mon, Nov 9, 2020 at 8:40 AM Amit Kapila wrote: > > > > On Mon, Nov 9, 2020 at 7:11 AM Michael Paquier wrote: > > > > > > /home/pgbfarm/buildroot/HEAD/pgsql.build/contrib/test_decoding/output_iso/results/concurrent_stream.out > > > 2020-11

pgsql: doc: Add note about pg_settings and customized options into cata

doc: Add note about pg_settings and customized options into catalogs.sgml. The pg_settings view does not display customized options until the extension module that defines them has been loaded. This commit add the note about that behavior, into the docs. Author: John Naylor Reviewed-by: Tom Lane,