Skip site navigation (1) Skip section navigation (2)

Re: cannot read pg_class without having selected a database / is this a bug?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: cannot read pg_class without having selected a database / is this a bug?
Date: 2011-12-03 22:37:07
Message-ID: CA+Tgmobc52X=11rwUWdTJcWFqwqcZE+5NAg5pxJqcxB_+0B8bA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2011/12/3 Tomas Vondra <tv(at)fuzzy(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Tomas VondraDate: 2011-12-03 23:02:20
Subject: Re: cannot read pg_class without having selected a database / is this a bug?
Previous:From: Tomas VondraDate: 2011-12-03 22:33:20
Subject: cannot read pg_class without having selected a database / is this a bug?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group