Re: [HACKERS] Runtime Partition Pruning
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] Runtime Partition Pruning |
Дата | |
Msg-id | CA+TgmoYbf=vAduPXkJ63tHWSnv6QdcCMdbXheJVF0RUUEe07qw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Runtime Partition Pruning (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: [HACKERS] Runtime Partition Pruning
|
Список | pgsql-hackers |
On Sat, Apr 7, 2018 at 5:13 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > I had reservations about a relation_open() in the new executor code. It > seemed a bit odd; we don't have any other relation_open in the executor > anywhere. However, setting up the pruneinfo needs some stuff from > relcache that I don't see a reasonable mechanism to pass through > planner. I asked Andres about it on IM and while he didn't endorse the > patch in any way, his quick opinion was that "it wasn't entirely > insane". I verified that we already hold lock on the relation. I don't get this. The executor surely had to (and did) open all of the relations somewhere even before this patch. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: