From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jorge E(dot) Alvarez" <demasiado(at)antisocial(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Pg_Dump Strange Error |
Date: | 2000-06-06 00:22:34 |
Message-ID: | 14389.960250954@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Jorge E. Alvarez" <demasiado(at)antisocial(dot)com> writes:
> I have a PostgreSQL 6.5.3 database server working flawlessly under
> Linux-Mandrake 7.0
> However, when I try to use the pg_dump utility, I get this error:
> #pg_dump myDatabase > backup.db
> NOTICE: get_groname: group 87 not found
> getTables(): SELECT failed. Explanation from backend: 'pqReadData() --
> backend closed the channel unexpectedly.
This is a known bug in 6.5 --- it doesn't cope with deleted groups
very gracefully. You have a table somewhere with GRANT permission
for a group number 87 that doesn't exist any longer, and the backend
crashes when pg_dump asks about the privileges on that table.
Easiest recovery method is probably to recreate a group with that
same number, eg
insert into pg_group values ('bogus', 87, '{}');
I believe this bug is fixed in 7.0.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-06 01:11:34 | Re: Re: Re: Speed of locating tables |
Previous Message | Lamar Owen | 2000-06-05 23:48:03 | Re: Anon CVS |