Re: CREATE PUBLICATION with 'publish_generated_columns' parameter specified but unassigned

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: CREATE PUBLICATION with 'publish_generated_columns' parameter specified but unassigned
Date: 2025-08-04 06:37:58
Message-ID: CAKFQuwYFV=D2zOST4Beue76Hms9zQRfFvOHhA0eKpXPZZtzVmQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday, August 3, 2025, Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
> Recently, I learned it is possible to say:
>
> CREATE PUBLICATION pub ... WITH (publish_generated_columns);
>
> This is equivalent to:
> CREATE PUBLICATION pub ... WITH (publish_generated_columns = stored);
>
>
> What is the verdict for this syntax -- ok or not?

Not.

An enum should not allow for an omitted value. The documented policy of
only booleans being allowed an optional value is what is expected. I’d say
this is a new-in-18 bug that should be fixed in the code. The
documentation is correct - absence of the option means “none”, presence
requires an explicit value and not its own missing-value default.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2025-08-04 06:49:40 Re: Improve pg_sync_replication_slots() to wait for primary to advance
Previous Message Thomas Munro 2025-08-04 06:34:41 Re: Potential deadlock in pgaio_io_wait()