pgsql: pg_dump: Remove obsolete trigger support

pg_dump: Remove obsolete trigger support Remove for dumping triggers from pre-9.2 servers. This should have been removed as part of 30e7c175b81. Reviewed-by: Tom Lane Discussion: https://www.postgresql.org/message-id/flat/56c8f5bf-de47-48c1-a592-588fb526e9e6%40eisentraut.org Branch -- mas

pgsql: doc: Update catalog documentation for attstattarget nullable

doc: Update catalog documentation for attstattarget nullable Fixup for 4f622503d6. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/556799660fc4dc23e187994ae5ea622933ea720f Modified Files -- doc/src/sgml/catalogs.sgml | 24 1 file

pgsql: Remove useless Assert

Remove useless Assert It's already included in the subsequent intVal() call. Fixup for 4f622503d6. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e3aa802e6f843fc8df793d2dccdafecc32fe2cfc Modified Files -- src/backend/commands/tablecmds.c | 1 - 1 file

pgsql: Escape output of pg_amcheck test

Escape output of pg_amcheck test The pg_amcheck test reports a skip message if the layout of the index does not match expectations. That message includes the bytes that were expected and the ones that were found. But the found ones are arbitrary bytes, which can have funny effects on the termina

pgsql: Add previous commit to .git-blame-ignore-revs.

Add previous commit to .git-blame-ignore-revs. Discussion: https://postgr.es/m/1393953.1698353...@sss.pgh.pa.us Discussion: https://postgr.es/m/cagjhlkoobec9mlsnb42d3co1vcmx71mlseuigeabbq8orda...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/36578f

pgsql: Re-pgindent catcache.c after previous commit.

Re-pgindent catcache.c after previous commit. Discussion: https://postgr.es/m/1393953.1698353...@sss.pgh.pa.us Discussion: https://postgr.es/m/cagjhlkoobec9mlsnb42d3co1vcmx71mlseuigeabbq8orda...@mail.gmail.com Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/

pgsql: Cope with catcache entries becoming stale during detoasting.

Cope with catcache entries becoming stale during detoasting. We've long had a policy that any toasted fields in a catalog tuple should be pulled in-line before entering the tuple in a catalog cache. However, that requires access to the catalog's toast table, and we'll typically do AcceptInvalidati

pgsql: Cope with catcache entries becoming stale during detoasting.

Cope with catcache entries becoming stale during detoasting. We've long had a policy that any toasted fields in a catalog tuple should be pulled in-line before entering the tuple in a catalog cache. However, that requires access to the catalog's toast table, and we'll typically do AcceptInvalidati

pgsql: Re-pgindent catcache.c after previous commit.

Re-pgindent catcache.c after previous commit. Discussion: https://postgr.es/m/1393953.1698353...@sss.pgh.pa.us Discussion: https://postgr.es/m/cagjhlkoobec9mlsnb42d3co1vcmx71mlseuigeabbq8orda...@mail.gmail.com Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/

pgsql: Cope with catcache entries becoming stale during detoasting.

Cope with catcache entries becoming stale during detoasting. We've long had a policy that any toasted fields in a catalog tuple should be pulled in-line before entering the tuple in a catalog cache. However, that requires access to the catalog's toast table, and we'll typically do AcceptInvalidati

pgsql: Re-pgindent catcache.c after previous commit.

Re-pgindent catcache.c after previous commit. Discussion: https://postgr.es/m/1393953.1698353...@sss.pgh.pa.us Discussion: https://postgr.es/m/cagjhlkoobec9mlsnb42d3co1vcmx71mlseuigeabbq8orda...@mail.gmail.com Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/

pgsql: Re-pgindent catcache.c after previous commit.

Re-pgindent catcache.c after previous commit. Discussion: https://postgr.es/m/1393953.1698353...@sss.pgh.pa.us Discussion: https://postgr.es/m/cagjhlkoobec9mlsnb42d3co1vcmx71mlseuigeabbq8orda...@mail.gmail.com Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/

pgsql: Cope with catcache entries becoming stale during detoasting.

Cope with catcache entries becoming stale during detoasting. We've long had a policy that any toasted fields in a catalog tuple should be pulled in-line before entering the tuple in a catalog cache. However, that requires access to the catalog's toast table, and we'll typically do AcceptInvalidati

pgsql: Re-pgindent catcache.c after previous commit.

Re-pgindent catcache.c after previous commit. Discussion: https://postgr.es/m/1393953.1698353...@sss.pgh.pa.us Discussion: https://postgr.es/m/cagjhlkoobec9mlsnb42d3co1vcmx71mlseuigeabbq8orda...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/96c019f

pgsql: Re-pgindent catcache.c after previous commit.

Re-pgindent catcache.c after previous commit. Discussion: https://postgr.es/m/1393953.1698353...@sss.pgh.pa.us Discussion: https://postgr.es/m/cagjhlkoobec9mlsnb42d3co1vcmx71mlseuigeabbq8orda...@mail.gmail.com Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/

pgsql: Cope with catcache entries becoming stale during detoasting.

Cope with catcache entries becoming stale during detoasting. We've long had a policy that any toasted fields in a catalog tuple should be pulled in-line before entering the tuple in a catalog cache. However, that requires access to the catalog's toast table, and we'll typically do AcceptInvalidati

pgsql: Cope with catcache entries becoming stale during detoasting.

Cope with catcache entries becoming stale during detoasting. We've long had a policy that any toasted fields in a catalog tuple should be pulled in-line before entering the tuple in a catalog cache. However, that requires access to the catalog's toast table, and we'll typically do AcceptInvalidati

pgsql: Make attstattarget nullable

Make attstattarget nullable This changes the pg_attribute field attstattarget into a nullable field in the variable-length part of the row. If no value is set by the user for attstattarget, it is now null instead of previously -1. This saves space in pg_attribute and tuple descriptors for most pr