Re: [HACKERS] WARNING: relcache reference leak: relation "p1" not closed

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] WARNING: relcache reference leak: relation "p1" not closed
Дата
Msg-id 9071.1488863082@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] WARNING: relcache reference leak: relation "p1" notclosed  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Ответы Re: [HACKERS] WARNING: relcache reference leak: relation "p1" notclosed  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Список pgsql-hackers
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> writes:
> Also, I found out that alter_table.sql mistakenly forgot to drop
> partitioned table "p1".  Patch 0002 takes care of that.

While that might or might not have been intentional, I think it's an
astoundingly bad idea to not leave any partitioned tables behind in
the final state of the regression database.  Doing so would likely
have meant that this particular bug evaded detection for much longer
than it did.  Moreover, it would mean that the pg_upgrade test would
have exactly no coverage of partitioned cases.

Therefore, there should definitely be a partitioned table, hopefully with
a less generic name than "p1", in the final regression DB state.  Whether
this particular one from alter_table.sql is a good candidate, I dunno.
But let's not drop it without adding a better-thought-out replacement.
        regards, tom lane



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

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: [HACKERS] WARNING: relcache reference leak: relation "p1" notclosed
Следующее
От: "Ideriha, Takeshi"
Дата:
Сообщение: Re: [WIP] RE: [HACKERS] DECLARE STATEMENT setting up a connectionin ECPG