| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'vignesh C' <vignesh21(at)gmail(dot)com> |
| Cc: | Zhijie Hou <houzhijie22(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: Test publication.sql racing with subscription.sql might fail due to cache lookup error |
| Date: | 2026-11-17 10:17:08 |
| Message-ID: | OS7PR01MB183171FFE2BE12115E0AE974CF57B2@OS7PR01MB18317.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
> The current error, cache lookup failed for relation, is an internal
> error and is not very helpful to the user. It would be better to
> report a clearer error, such as relation may have been dropped
> concurrently, when the caller cannot tolerate a missing relation. If
> the caller can tolerate it, the missing child relation could simply be
> skipped.
Thanks for the confirmation. We may be able to introduce an attribute like
"missing_ok", but can be discussed other places. Because it affects broader areas.
v3 directly skips relations which have already been dropped, looks
enough. LGTM.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maksim.Melnikov | 2026-11-17 10:52:30 | Re: race condition when writing pg_control |
| Previous Message | shveta malik | 2026-11-17 10:09:32 | Re: Initial table sync copies the whole table when it is no longer published |