Re: Support EXCEPT for ALL SEQUENCES publications

From: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
To: Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Support EXCEPT for ALL SEQUENCES publications
Date: 2026-07-03 05:53:52
Message-ID: CAE9k0PndRsogmPEpYrm5CrT1wWHO5dWaq90vcsP_po_zaYo37A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Thu, Jul 2, 2026 at 11:53 AM Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com> wrote:
>
> Please find the updated v17 patch attached.
>

Thank you for the updated patches. I see that the following command
works with your patch:

CREATE PUBLICATION combined_seq_pub_1
FOR ALL SEQUENCES
EXCEPT (SEQUENCE ONLY s1_seq);

May I know what the purpose of ONLY is here?

AFAIU, for FOR ALL TABLES, ONLY was added to handle inherited tables.
However, sequences do not have inheritance, so I am not sure what
semantics ONLY is intended to provide for sequences. Could you please
clarify?

--
With Regards,
Ashutosh Sharma.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Feng Wu 2026-07-03 06:03:06 Re: [PATCH v2] Avoid internal error for invalid interval typmods
Previous Message Bertrand Drouvot 2026-07-03 05:52:44 Re: Re-read subscription state after lock in AlterSubscription