Re: WARNING: relcache reference leak: relation "p1" not closed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Grittner <kgrittn(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: WARNING: relcache reference leak: relation "p1" not closed
Date: 2017-03-06 22:28:57
Message-ID: 27640.1488839337@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Grittner <kgrittn(at)gmail(dot)com> writes:
> With e434ad39ae7316bcf35fd578dd34ad7e1ff3c25f I did a `make world`,
> `make install-world`, a fresh default initdb, a start with default
> config, `make installcheck`, connected to the regression database
> with psql as the initial superuser, and ran:

> regression=# vacuum freeze analyze;
> WARNING: relcache reference leak: relation "p1" not closed
> VACUUM

p1 is a partitioned table. (BTW, could I lobby for people not to use such
generic, collision-prone names for tables that will be left behind after
the regression tests?) Also, I find that "vacuum analyze" is sufficient,
or even just "analyze", or "analyze p1". I think it's highly likely this
was introduced by 3c3bb99330aa9b4c2f6258bfa0265d806bf365c3. Certainly
that failed to add appropriate regression test cases, or we would have
noticed this already.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-03-06 22:30:11 Re: Need a builtin way to run all tests faster manner
Previous Message Andres Freund 2017-03-06 22:19:29 Re: Performance degradation in TPC-H Q18