Re: [HACKERS] Odd problem with pg_class ...

Okay, figured it out...

The problem exists in v6.5.x as well.

Basically, the user had, it seems, accidentally deleted various groups
from pg_group, which he had used to GRANT group permissions on various
tables, causing an error message of:

NOTICE:  get_groname: group 185 not found

to be printed to his errlog.

In v6.5.x, you at least get something out through psql when you do this,
but should we get:

==========================| status           | {"=","group keystone=arwR"}
|+------------------+-----------------------------+
pgsql_keystone=> delete from pg_group where groname='keystone';
DELETE 1
pgsql_keystone=> \z
NOTICE:  get_groname: group 0 not found
pqReadData() -- backend closed the channel unexpectedly.       This probably means the backend terminated abnormally
  before or while processing the request.
 
===========================

Doesn't sound very "friendly"...


On Thu, 2 Sep 1999, The Hermit Hacker wrote:

> 
> Morning all...
> 
>     Am looking at a v6.4 system, and if I do:
> 
> select relname from pg_class;
> 
>     It returns all the relations...but if I do:
> 
> select relname,relacl from pg_class;
> 
>     It gives me:
> 
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally before or
> while processing the request. We have lost the connection to the backend,
> so further processing is impossible.  Terminating.
> 
>     Still investigating, but if anyone has any suggestions, I'm all
> ears...
> 
> Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
> Systems Administrator @ hub.org 
> primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 
> 
> 
> ************
> 

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org