Re: Skipping schema changes in publication - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Skipping schema changes in publication
Date
Msg-id CAA4eK1+4ZNF-MGheeTtYF9TdfNBnKKJ8DivWZsXBnuJVkqfa0g@mail.gmail.com
Whole thread Raw
In response to Re: Skipping schema changes in publication  (Shlok Kyal <shlok.kyal.oss@gmail.com>)
Responses Re: Skipping schema changes in publication
List pgsql-hackers
On Fri, Mar 27, 2026 at 1:20 PM Shlok Kyal <shlok.kyal.oss@gmail.com> wrote:
>
> I have addressed the comments. Attached the updated patch.
>

I got following crash:

postgres=# create publication pub1 for all tables except (t1, t2);
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.

Server Log:
 ERROR:  syntax error at or near "table" at character 47
[client backend] STATEMENT:  create publication pub1 for all tables
except table (t1, t2);
TRAP: failed Assert("pubobj->pubobjtype ==
PUBLICATIONOBJ_EXCEPT_TABLE"), File: "../src/backend/parser/gram.y",
Line: 20795, PID: 7512
abort() has been called[postmaster] LOG:  client backend (PID 7512)
was terminated by exception 0xC0000409
[postmaster] DETAIL:  Failed process was running: create publication
pub1 for all tables except (t1, t2);
[postmaster] HINT:  See C include file "ntstatus.h" for a description
of the hexadecimal value.

BTW, why do we need preprocess_except_pubobj_list?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Define DatumGetInt8 function.
Next
From: Nisha Moond
Date:
Subject: Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion?