| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Darryl Green <darryl(dot)green(at)gmail(dot)com> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Partitioning, Identity and Uniqueness (given pg 16 changes) |
| Date: | 2024-02-19 14:11:25 |
| Message-ID: | CAKFQuwZ1D3to93Jy_R5xhotbugh0auTbfagRBOO+HBRFKGH77w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday, February 19, 2024, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Monday, February 19, 2024, Darryl Green <darryl(dot)green(at)gmail(dot)com> wrote:
>
>>
>> > It may be possible to still have it work by doing a speculative record
>> > in the index for the target table then go and check all of the other
>> > indexes before marking the speculative entry as valid.
>>
>> It is always valid - except in the OVERRIDING SYSTEM VALUE case - no?
>>
>
> False.
>
> ALTER TABLE … ALTER id RESTART 1;
>
Even without a reset as soon as you override system value at least one
future non-override insert is going to fail when the sequence catches up to
whatever that non-overridden value was.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Johnathan Tiamoh | 2024-02-19 16:59:20 | DETAIL: Could not open file "pg_xact/0EEA": No such file or directory |
| Previous Message | David G. Johnston | 2024-02-19 14:07:05 | Re: Partitioning, Identity and Uniqueness (given pg 16 changes) |