Search Postgresql Archives

Re: Partitioning, Identity and Uniqueness (given pg 16 changes)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Monday, February 19, 2024, David G. Johnston <david.g.johnston@xxxxxxxxx> wrote:
On Monday, February 19, 2024, Darryl Green <darryl.green@xxxxxxxxx> 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.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux