Re: rehashing catalog cache id 14 for pg_opclass; 17 tups, 8 buckets

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: rehashing catalog cache id 14 for pg_opclass; 17 tups, 8 buckets
Date: 2018-04-17 20:55:53
Message-ID: a35f8240-89d1-34b3-cf92-d11ee29a441a@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 04/17/2018 01:14 PM, Thiemo Kellner wrote:
> Hi all
>
> When running following query in psql (server and client version 10 with
> replication on Debian 9), I get the message mentioned in the subject. I
> have not found much searching the internet. There were suggestions on
> bloat so I ran "vacuum (verbose, full, analyze)" but the message remains.
>

>
> I do not feel that my DB has a problem but I was taken aback a bit when
> I first saw the message in the subject.
>
> I would be grateful about a bit shed light.

What do you have your log levels set to?

The only place I can find this message is in:

src/backend/utils/cache/catcache.c

elog(DEBUG1, "rehashing catalog cache id %d for %s; %d tups, %d buckets",
cp->id, cp->cc_relname, cp->cc_ntup, cp->cc_nbuckets);

If I am following correctly it is fairly low level message.

>
> Kind regards Thiemo
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Hans Sebastian 2018-04-18 00:02:31 Old active connections?
Previous Message Paul Jungwirth 2018-04-17 20:49:13 Re: array UNNESTed to rows stable with respect to order?