Re: crash with sql language partition support function
От | Ashutosh Bapat |
---|---|
Тема | Re: crash with sql language partition support function |
Дата | |
Msg-id | CAFjFpRdOGmj5XVBr3PrPVfQ2wU=A1WOiLwcgA3hZCnmEAz3d2Q@mail.gmail.com обсуждение исходный текст |
Ответ на | crash with sql language partition support function (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>) |
Ответы |
Re: crash with sql language partition support function
|
Список | pgsql-hackers |
On Tue, Apr 10, 2018 at 1:44 PM, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote: > > Attached fixes it. It teaches RelationBuildPartitionKey() to use > fmgr_info_cxt and pass rd_partkeycxt to it. The patch is using partkeycxt and not rd_partkeycxt. Probably a typo in the mail. But a wider question, why that context? I guess that cache context will vanish when that cache entry is thrown away. That's the reason we have to copy partition key information in find_partition_scheme() instead of just pointing to it and also use fmgr_info_copy() there. But if that's the case, buildfarm animal run with -DCLOBBER_CACHE_ALWAYS should show failure. I am missing something here. -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
В списке pgsql-hackers по дате отправления: