RE: Skip partition tuple routing with constant partition key
От | houzj.fnst@fujitsu.com |
---|---|
Тема | RE: Skip partition tuple routing with constant partition key |
Дата | |
Msg-id | OS0PR01MB57169DEA5CFDC23A1F4A832D94239@OS0PR01MB5716.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: Skip partition tuple routing with constant partition key (Amit Langote <amitlangote09@gmail.com>) |
Ответы |
Re: Skip partition tuple routing with constant partition key
|
Список | pgsql-hackers |
From: Amit Langote <amitlangote09@gmail.com> Sent: Thursday, May 27, 2021 1:54 PM > On Thu, May 27, 2021 at 11:47 AM houzj.fnst@fujitsu.com > <houzj.fnst@fujitsu.com> wrote: > > About teaching relcache about caching the target partition. > > > > David-san suggested cache the partidx in PartitionDesc. > > And it will need looping and checking the cached value at each level. > > I was thinking can we cache a partidx list[1, 2 ,3], and then we can > > follow the list to get the last partition and do the partition CHECK > > only for the last partition. If any unexpected thing happen, we can > > return to the original table and redo the tuple routing without using the > cached index. > > What do you think ? > > Where are you thinking to cache the partidx list? Inside PartitionDesc or some > executor struct? I was thinking cache the partidx list in PartitionDescData which is in relcache, if possible, we can use the cached partition between statements. Best regards, houzj
В списке pgsql-hackers по дате отправления: