> you end up burning an auto incremented key. Curious to see what PG ends up doing here I haven't tried, but Postgres always uses values in sequences in simila

> you end up burning an auto incremented key. Curious to see what PG ends up doing here I haven't tried, but Postgres always uses values in sequences in similar cases. The good news is that there are so many values in a 64 bit sequence that this really shouldn't matter. I much prefer some values in sequences to be not used over even the tiniest possibility of a value being used twice accidentally.