Re: why partition pruning doesn't work?
От | Robert Haas |
---|---|
Тема | Re: why partition pruning doesn't work? |
Дата | |
Msg-id | CA+TgmoaQ+hxgDP4uxP_nRgC+JAn33_vona8P+GAnRDkceSZNSw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: why partition pruning doesn't work? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: why partition pruning doesn't work?
|
Список | pgsql-hackers |
On Wed, Jun 13, 2018 at 12:15 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> As for whether to change it at this point in the release cycle, I >> guess that, to me, depends on how invasive the fix is. > > It seems not to be that bad: we just need a shutdown call for the > PartitionPruneState, and then we can remember the open relation there. > The attached is based on David's patch from yesterday. Seems reasonable. Really, I think we should look for a way to hang onto the relation at the point where it's originally opened and locked instead of reopening it here. But that's probably more invasive than we can really justify right at the moment, and I think this is a step in a good direction. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: