Re: Skip partition tuple routing with constant partition key - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Skip partition tuple routing with constant partition key
Date
Msg-id CAM-w4HO3+v2Jtxc5P4eWB5DW9m4vyfUJb8eR9c8Akcf3SSMJgQ@mail.gmail.com
Whole thread Raw
In response to Re: Skip partition tuple routing with constant partition key  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: Skip partition tuple routing with constant partition key  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
There are a whole lot of different patches in this thread.

However this last one https://commitfest.postgresql.org/37/3270/
created by Amit seems like a fairly straightforward optimization that
can be evaluated on its own separately from the others and seems quite
mature. I'm actually inclined to set it to "Ready for Committer".

Incidentally a quick read-through of the patch myself and the only
question I have is how the parameters of the adaptive algorithm were
chosen. They seem ludicrously conservative to me and a bit of simple
arguments about how expensive an extra check is versus the time saved
in the boolean search should be easy enough to come up with to justify
whatever values make sense.



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: do only critical work during single-user vacuum?
Next
From: Magnus Hagander
Date:
Subject: Re: Estimating HugePages Requirements?