Re: tableam scan-API patch broke foreign key validation

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: tableam scan-API patch broke foreign key validation
Дата
Msg-id 20190408055440.x2xkdsnpg7qi4kxn@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: tableam scan-API patch broke foreign key validation  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Hi,

On 2019-04-06 14:43:26 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2019-04-06 14:34:34 -0400, Tom Lane wrote:
> >> Why should this code need to free anything?  That'd be the responsibility
> >> of the slot code, no?
> 
> > Well, not really. If a slot doesn't hold heap tuples internally,
> > ExecFetchSlotHeapTuple() will return a fresh heap tuple (but signal so
> > by setting *should_free = true if not NULL).
> 
> Ah, got it: ignoring should_free is indeed a potential issue here.

I've pushed a revised version of my earlier patch adding a memory
context that's reset after each tuple.

Greetings,

Andres Freund



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Shouldn't validateForeignKeyConstraint() reset memory context?
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: reloption to prevent VACUUM from truncating empty pages at theend of relation