Re: BUG #18618: pg_upgrade from 14 to 15+ fails for unlogged table with identity column - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18618: pg_upgrade from 14 to 15+ fails for unlogged table with identity column
Date
Msg-id 1680623.1726602973@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18618: pg_upgrade from 14 to 15+ fails for unlogged table with identity column  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
I wrote:
>> The only alternative I can see is to extend the ALTER TABLE ADD
>> GENERATED syntax to allow correct specification of the sequence's
>> LOGGED/UNLOGGED status to begin with.  While cleaner, that would be
>> a lot more work and probably result in compatibility problems for
>> normal uses of pg_dump (where the output might get loaded into a
>> server version that lacks the syntax extension).

> So we have to do it like that, and it seems not that bad, especially
> if we follow the lead of the SEQUENCE NAME option and don't bother
> to document this stuff.  (I don't think that's a great precedent,
> but I didn't change it here.)

Pushed with a bit of further polishing, including adding that
missing documentation.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: PL/pgSQL THEN binging in condition
Next
From: Tom Lane
Date:
Subject: Re: PL/pgSQL THEN binging in condition