| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Michael Corey <michael(dot)corey(dot)ap(at)nielsen(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Identity and Sequence |
| Date: | 2024-02-16 16:34:32 |
| Message-ID: | CAKFQuwZGyW+Gn1_Wa6e5=NtTpsnmVgH=6JV516M8r+J4rjyVHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Feb 16, 2024 at 9:24 AM Michael Corey <michael(dot)corey(dot)ap(at)nielsen(dot)com>
wrote:
> If I run these two statements I get an error
> ERROR: relation "part_tab_part_id_seq" already exists
>
> I tried different combinations of this ALTER TABLE statement and none seem
> to work. What is the proper way to reattach the identity and the sequence
> bearing in mind that I will load the new table with the data from the old
> table?
>
>
So remove the generated by default from the old non-partitioned table
(manually drop the sequence if needed too'. Or just choose a different
sequence name for the new one.
"reattach the identity" isn't a thing - the system is telling you it is
creating a new one and you will need to synchronize it to your data.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2024-02-16 17:20:01 | Re: Encryption Options |
| Previous Message | Michael Corey | 2024-02-16 16:23:44 | Identity and Sequence |