Re: pg_group_name_index corrupt?

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_group_name_index corrupt?
Date: 2000-05-05 03:36:25
Message-ID: Pine.BSF.4.21.0005050035160.56194-100000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 4 May 2000, Tom Lane wrote:

> The Hermit Hacker <scrappy(at)hub(dot)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 ...

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-05-05 03:40:04 Re: client libpq multibyte support
Previous Message Don Baccus 2000-05-05 03:34:21 Re: ``..Advice For New Immigrants...