From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Hoffmann <jeff(at)propertykey(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Problem with identity column & related sequences |
Date: | 2021-09-28 19:13:27 |
Message-ID: | 2870866.1632856407@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jeff Hoffmann <jeff(at)propertykey(dot)com> writes:
> I am using postgresql-12.8. I am using I am making use of an identity
> column for part of a scripts to process some updated data. Because of
> the way the script is called I don't necessarily know if this column
> is going to exist in the table I am working on so I have a step that
> will conditionally create the column if it doesn't already exist, i.e.
> alter table mytable add column if not exists unique_id integer
> generated always as identity;
You're right, this sort of thing does not work very well in v12 and
before. We fixed it in v13, but the changes seemed far too invasive
to risk a back-patch [1].
regards, tom lane
[1] https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=1281a5c90
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Hoffmann | 2021-09-28 19:35:06 | Re: Problem with identity column & related sequences |
Previous Message | Jeff Hoffmann | 2021-09-28 18:38:47 | Problem with identity column & related sequences |