Re: pg_group_name_index corrupt? - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: pg_group_name_index corrupt?
Date
Msg-id Pine.BSF.4.21.0005050035160.56194-100000@thelab.hub.org
Whole thread Raw
In response to Re: pg_group_name_index corrupt?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_group_name_index corrupt?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 4 May 2000, Tom Lane wrote:

> The Hermit Hacker <scrappy@hub.org> writes:
> >> I griped about that a week or so ago, but no one seems to have picked up
> >> on it.  Do you want to consider that a "must fix" problem as well?
> >> I think it's a pretty minor fix, but considering how late we are in the
> >> cycle...
> 
> > considering where the problem is, I think that if it can be safely done,
> > please do it ...
> 
> Done and done.  I also realized that pg_upgrade had another nasty bug
> in it: the VACUUMs were not necessarily executed as superuser, but as
> whichever user happened to own the item dumped last by pg_dump in each
> database.  That would result in VACUUM skipping over tables it thought
> it didn't have permission to vacuum --- like, say, all the system
> tables.  Perhaps this explains the failures that some people have
> reported.
> 
> Another day, another bug swatted ...

Okay, before I package this up and annouce it ... I just posted something
that I *think* is probably related, but just want to make sure ... if I do
a pg_dump of a database, i'm getting an ERROR about 'Inhrel' Attribute not
found ... not sure why, or if it matters ...




pgsql-hackers by date:

Previous
From: Don Baccus
Date:
Subject: Re: ``..Advice For New Immigrants...
Next
From: Tom Lane
Date:
Subject: Re: client libpq multibyte support