Re: cannot read pg_class without having selected a database / is this a bug? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: cannot read pg_class without having selected a database / is this a bug?
Date
Msg-id CA+Tgmobc52X=11rwUWdTJcWFqwqcZE+5NAg5pxJqcxB_+0B8bA@mail.gmail.com
Whole thread Raw
In response to cannot read pg_class without having selected a database / is this a bug?  (Tomas Vondra <tv@fuzzy.cz>)
Responses Re: cannot read pg_class without having selected a database / is this a bug?  (Tomas Vondra <tv@fuzzy.cz>)
List pgsql-hackers
2011/12/3 Tomas Vondra <tv@fuzzy.cz>:
> psql: FATAL:  cannot read pg_class without having selected a database
>
> I've found this happens because the extension defines a client auth hook
> that reads pg_stat_activity. The really interesting thing is that this
> happens only when I start several backends 'at the same time' right
> after the cluster is started. From that time, everything works just fine.

I'm surprised this ever works.  To read pg_stat_activity, you need a
relcache entry for it.  And how will you build one without selecting a
database?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: cannot read pg_class without having selected a database / is this a bug?
Next
From: Tomas Vondra
Date:
Subject: Re: cannot read pg_class without having selected a database / is this a bug?