Re: Support EXCEPT for TABLES IN SCHEMA publications

From: shveta malik <shveta(dot)malik(at)gmail(dot)com>
To: Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Subject: Re: Support EXCEPT for TABLES IN SCHEMA publications
Date: 2026-07-01 10:16:43
Message-ID: CAJpy0uD=deQJxbEuug-fbhvG6K47w1k_dwkZvbhAaBbBAgUPeg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 1, 2026 at 3:37 PM Nisha Moond <nisha(dot)moond412(at)gmail(dot)com> wrote:
>
>
> Besides the above comments, I found and fixed a few additional issues
> during further testing:
> 1) Fixed an issue where UPDATE/DELETE on an excluded table without
> replica identity was still blocked. e.g.,
>
> postgres=# create publication pub_h2 for tables in schema s1 except ( table t1);
> postgres=# update s1.t1 set c1=3 where c1=1;
> ERROR: cannot update table "t1" because it does not have a replica
> identity and publishes updates
> HINT: To enable updating the table, set REPLICA IDENTITY using ALTER TABLE.
>
> Excluded tables should not be treated as published for update/delete checks.

Nisha, this bug was introduced by your patch or does it exist in 'ALL
TABLES Except TABLE' too?

thanks
Shveta

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2026-07-01 10:24:19 Re: Support EXCEPT for TABLES IN SCHEMA publications
Previous Message Nisha Moond 2026-07-01 10:12:38 Re: Support EXCEPT for TABLES IN SCHEMA publications