Re: pg_dump fails to set index ownership

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump fails to set index ownership
Date: 2005-09-23 21:46:08
Message-ID: 20050923214608.GA3106@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 23, 2005 at 04:45:02PM -0400, Bruce Momjian wrote:
> Tom Lane wrote:
> > Michael Fuhr <mike(at)fuhr(dot)org> writes:
> > > Regarding the removal of ALTER INDEX OWNER commands from pg_dump,
> > > indexes are now restored with the wrong ownership if the user doing
> > > the restore is different than the user who owned the original index
> >
> > pg_dump is not the source of the problem. We should instead arrange
> > that an index's relowner value is copied directly from the parent table
> > during CREATE INDEX. This is probably more important now with roles,
> > since GetUserId() might not have a lot to do with the table's owner ID.
>
> My testing indicated this is fixed.

Tom fixed it shortly after making that post:

http://archives.postgresql.org/pgsql-committers/2005-08/msg00347.php

--
Michael Fuhr

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-09-23 22:00:05 Re: ALTER ROLES - questions
Previous Message Bruce Momjian 2005-09-23 21:44:26 Re: [COMMITTERS] pgsql: Basic documentation for ROLEs.