Re: pg_dump fails to set index ownership

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump fails to set index ownership
Date: 2005-08-25 21:56:16
Message-ID: 25715.1125006976@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2005-08-25 22:01:25 Re: Stuff running slooow
Previous Message Tom Lane 2005-08-25 21:51:24 Re: [HACKERS] Proposed patch to getaddrinfo.c to support