diff options
| author | Amit Kapila <akapila@postgresql.org> | 2025-02-20 11:25:29 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2025-02-20 11:25:29 +0530 |
| commit | 4aa6fa3cd0a2422f1bb47db837b82f2b53d4c065 (patch) | |
| tree | d4f4a8abf5248c160f90e12ff584fd37b34493bf /src/backend/tcop/postgres.c | |
| parent | f11674f8dfe811390dfeaf6f3c3a554dbeb790e1 (diff) | |
| download | postgresql-4aa6fa3cd0a2422f1bb47db837b82f2b53d4c065.tar.gz postgresql-4aa6fa3cd0a2422f1bb47db837b82f2b53d4c065.zip | |
Include schema/table publications even with exclude options in dump.
The current implementation inconsistently includes public schema but not
information_schema when those are specified in FOR TABLES IN SCHMEA ...
Apart from that, the current behavior for publications w.r.t exclude table
and schema (--exclude-table, --exclude-schema) option differs from what we
do at other places. We try to avoid including publications for
corresponding tables or schemas when an exclude-table or exclude-schema
option is given, unlike what we do for views using functions defined in a
particular schema or a subscription pointing to publications with their
corresponding exclude options.
I decided not to backpatch this as it leads to a behavior change and we don't
see any field report for current behavior.
Reported-by: Tom Lane <tgl@sss.pgh.pa.us>
Author: Vignesh C <vignesh21@gmail.com>
Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>
Discussion: https://postgr.es/m/1270733.1734134272@sss.pgh.pa.us
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions