| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Distinguish publication exclusions in object addresses |
| Date: | 2026-09-16 07:34:03 |
| Message-ID: | CAA4eK1++NMJbD4aiahiH6N8kx01-MEcC87KPMZ_BBvK_qTdmqA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 16, 2026 at 12:46 PM Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
> In this experiment below I got an unexpected result.
> - Is it a bug?
>
Possible but not related to this patch. Even the following simple test
without patch gives the same result:
postgres=# CREATE TABLE t1(a int);
CREATE TABLE
postgres=# CREATE PUBLICATION pub FOR ALL TABLES;
CREATE PUBLICATION
postgres=# SELECT pg_get_object_address('publication
relation','{public,t1}','{pub}');
ERROR: publication relation "t1" in publication "pub" does not exist
I suggest starting a new thread to discuss this case.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2026-09-16 07:37:36 | Re: Distinguish publication exclusions in object addresses |
| Previous Message | Osama Abdul Qader | 2026-09-16 07:27:54 | Re: Severe performance degradation with concurrent updates due to excessive EvalPlanQual (EPQ) re‑evaluation |