| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WARNING: relcache reference leak: relation "p1" not closed |
| Date: | 2017-03-08 01:55:57 |
| Message-ID: | b540619a-a478-470c-12f2-1ae519fee167@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-03-08 01:56:40 | Re: PATCH: Batch/pipelining support for libpq |
| Previous Message | Amit Langote | 2017-03-08 01:39:01 | Re: Example Custom Scan Provider Implementation? |