Re: BUG #15640: FATAL: XX000: cannot read pg_class without having selected a database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: m(dot)kiianov(at)rtk-dc(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: BUG #15640: FATAL: XX000: cannot read pg_class without having selected a database
Date: 2019-02-18 16:29:49
Message-ID: 28802.1550507389@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2019-Feb-18, PG Bug reporting form wrote:
>> 2019-02-18 05:30:36 GMT [40378]: [2-1] db=,user= FATAL: XX000: cannot read pg_class without having selected a database
>> 2019-02-18 05:30:36 GMT [40378]: [3-1] db=,user= LOCATION: ScanPgRelation, relcache.c:314

> Hmm, I wonder if this is a bug introduced in 6a46aba1cd6d (in 9.6.10)
> that only hits autovacuum launcher after a relcache init removal at just
> the wrong time, or something like that?

I think/hope that the launcher isn't connected to sinval, either.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2019-02-18 16:42:47 Re: BUG #15640: FATAL: XX000: cannot read pg_class without having selected a database
Previous Message Stephen Frost 2019-02-18 16:26:38 Re: BUG #15636: PostgreSQL 11.1 pg_basebackup backup to a CIFS destination throws fsync error at end of backup