pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jens Hartwig <jhartwig@debis.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Damaged table "pg_access"
Date: Wed, 29 Nov 2000 07:18:37 +0100
Message-ID: <3A249FBD.F99C5C0C@debis.com> (raw)
References: <3A2366CE.5FB828E@debis.com>
	<14900.975423998@sss.pgh.pa.us>

Hello,

yes, you were completely right, thank you very much, you saved me from
spending much time on this problem! The recreation of the groups 1, 2, 3
and 4 resolved the problem :-) My next question is: how can I (as a
workaround till version 7.1) permanently remove a group without facing
this problem? Can I rudely remove the granted permissions by any command
(e.g. deleting it manually from the system catalogue)?

Best regards, Jens

Tom Lane schrieb:
> 
> Jens Hartwig <jhartwig@debis.com> writes:
> > when I try to access the system-table "pg_class", I get the following
> > error:
> 
> > zeda=# select * from pg_class;
> > NOTICE:  get_groname: group 1 not found
> > pqReadData() -- backend closed the channel unexpectedly.
> 
> Evidently you had created a group with sysid 1, granted some permissions
> on some table to that group, and then deleted the group.  Re-create the
> group (CREATE GROUP foo WITH SYSID 1).
> 
> I thought the crash in this situation had been fixed long since, but
> apparently not :-( ... it still fails in current sources.  I'll make
> sure it's fixed for 7.1.
> 
>                         regards, tom lane

=============================================
Jens Hartwig
---------------------------------------------
debis Systemhaus GEI mbH
10875 Berlin
Tel.     : +49 (0)30 2554-3282
Fax      : +49 (0)30 2554-3187
Mobil    : +49 (0)170 167-2648
E-Mail   : jhartwig@debis.com
=============================================



view thread (4+ messages)  latest in thread

Message-ID: <3A249FBD.F99C5C0C@debis.com>
Permalink:  ../3A249FBD.F99C5C0C@debis.com/
Also on:    postgresql.org/message-id/3A249FBD.F99C5C0C@debis.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: jhartwig@debis.com, tgl@sss.pgh.pa.us
  Subject: Re: Damaged table "pg_access"
  In-Reply-To: <3A249FBD.F99C5C0C@debis.com>
  References: <3A2366CE.5FB828E@debis.com> <14900.975423998@sss.pgh.pa.us> <3A249FBD.F99C5C0C@debis.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox