parameters - Search results
Mailing lists >> pgsql-patches >> Thread
2008-09-23 10:13:45 | Re: hash index improving v3 (Tom Lane)
this is really worth arguing about, much less exposing a separate parameter for. regards, tom lane
Mailing lists >> pgsql-patches >> Thread
2008-09-23 10:04:29 | Re: hash index improving v3 (Simon Riggs)
parameter, but even if we had a parameter it would be very difficult to set it. Thinks
Mailing lists >> pgsql-patches >> Thread
2008-09-23 09:17:03 | Re: hash index improving v3 (Tom Lane)
memory allocation parameter; it's a switchover threshold between two different behaviors. regards, tom lane
Mailing lists >> pgsql-patches >> Thread
2008-09-23 01:48:57 | Re: hash index improving v3 (Tom Lane)
parameter; but seeing that we still don't have all that much of a use case
Mailing lists >> pgsql-patches >> Thread
2008-09-23 01:30:32 | Re: hash index improving v3 (Simon Riggs)
parameter instead. At the very least, a controllable parameter is the only appropriate choice for production
Mailing lists >> pgsql-patches >> Thread
2008-09-09 10:48:54 | Re: hash index improving v3 (Kenneth Marshall)
parameters like fillfactor to accomodate these sorts of situations. Since your test cuts the effective