| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | Marco Slot <marco(at)citusdata(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Dave Cramer <davecramer(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How is this possible "publication does not exist" |
| Date: | 2020-12-24 12:38:03 |
| Message-ID: | 07992a67-945a-8e78-485f-94daf45a6c9b@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/24/20 12:50 PM, Marco Slot wrote:
> I've been running into a similar issue and am a little puzzled by it,
> especially since it survives restarts.
>
Interesting. Which PostgreSQL version are you using? Any idea how to
reproduce it? Were there any failures right before the issue appeared?
I wonder if this might be a case of index corruption. Can you try
forcing an index scan on pg_publication?
SET enable_seqscan = false;
SET enable_bitmapscan = off;
SELECT * FROM pg_publication WHERE pubname = 'migration_pub';
Also, it might be helpful to know why get_rel_sync_entry ended up
calling LoadPublications - did we just create the entry?
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2020-12-24 12:49:51 | Re: Preventing hangups in bgworker start/stop during DB shutdown |
| Previous Message | Ashutosh Bapat | 2020-12-24 12:26:44 | Re: Feature request: Connection string parsing for postgres_fdw |