I don't know if it will necessarily be of much use in partition pruning,
but it should work fairly well as a choice of clustered primary key
together with block range indexes.
On Wed, Oct 22, 2025 at 12:53 PM Jonathan Reis
wrote:
> Hello PostgreSQL performance team,
>
> I’m evaluating the new UU
On Wed, 22 Oct 2025 at 23:53, Jonathan Reis wrote:
> Will the planner efficiently prune partitions when queries filter by UUIDv7
> ranges (e.g., WHERE id BETWEEN uuidv7_floor(timestamp1) AND
> uuidv7_floor(timestamp2) that align with time periods?
It depends. What are timestamp1 and timestamp2?
Hello PostgreSQL performance team,
I’m evaluating the new UUIDv7 type in PostgreSQL v18 and would like advice
on its suitability for time-based partitioning and related planner behavior.
*Context*
I have a large message/event table where each row is identified by a uuidv7
primary key. Because UUI
