diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2017-06-20 12:25:07 -0400 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2017-06-20 12:35:02 -0400 |
| commit | a2141c42f9ebc51b4501a4fafea9dd3fb7eda23d (patch) | |
| tree | 6a273b7f730515593cdd6ba0e6fa8e19575d3e59 /src/backend/access/gist/gistbuild.c | |
| parent | 20d7d68b098dde6106e6c382e787c8b10c4403df (diff) | |
| download | postgresql-a2141c42f9ebc51b4501a4fafea9dd3fb7eda23d.tar.gz | |
Tweak publication fetching in psql
Viewing a table with \d in psql also shows the publications at table is
in. If a publication is concurrently dropped, this shows an error,
because the view pg_publication_tables internally uses
pg_get_publication_tables(), which uses a catalog snapshot. This can be
particularly annoying if a for-all-tables publication is concurrently
dropped.
To avoid that, write the query in psql differently. Expose the function
pg_relation_is_publishable() to SQL and write the query using that.
That still has a risk of being affected by concurrent catalog changes,
but in this case it would be a table drop that causes problems, and then
the psql \d command wouldn't be interesting anymore anyway.
Reported-by: Tom Lane <tgl@sss.pgh.pa.us>
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions