Re: [HACKERS] WARNING: relcache reference leak: relation "p1" notclosed - Mailing list pgsql-hackers

From Amit Langote
Subject Re: [HACKERS] WARNING: relcache reference leak: relation "p1" notclosed
Date
Msg-id b540619a-a478-470c-12f2-1ae519fee167@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS] WARNING: relcache reference leak: relation "p1" not closed  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2017/03/08 1:34, Robert Haas wrote:
> On Tue, Mar 7, 2017 at 1:43 AM, Amit Langote wrote:
>> On 2017/03/07 14:04, Tom Lane wrote:
>>> 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.
>>
>> OK, let's drop p1 in alter_table.sql.  I think a partitioned table created
>> in insert.sql is a good candidate to keep around after having it renamed,
>> which patch 0003 does.
> 
> Committed 0001.
> 
> Committed 0002 and 0003 together.

Thanks.

Regards,
Amit





pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [HACKERS] Example Custom Scan Provider Implementation?
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] PATCH: Batch/pipelining support for libpq