Re: pg_dump fails to set index ownership

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

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.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-09-23 20:47:38 Re: pg_dump fails to set index ownership
Previous Message Bruce Momjian 2005-09-23 20:32:05 Re: Improved \df(+) in psql + backward-compatibility