Re: ALTER INDEX OWNER TO - Mailing list pgsql-hackers

From ohp@pyrenet.fr
Subject Re: ALTER INDEX OWNER TO
Date
Msg-id Pine.UW2.4.53.0508151657110.12006@sun.pyrenet
Whole thread Raw
In response to Re: ALTER INDEX OWNER TO  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
pg_dump is STILL emiting alter index.
ISTM we shou make it a warning AND remove it from pg_dump
Regards
On Mon, 15 Aug 2005, Tom Lane wrote:

> Date: Mon, 15 Aug 2005 09:54:12 -0400
> From: Tom Lane <tgl@sss.pgh.pa.us>
> To: ohp@pyrenet.fr
> Cc: pgsql-hackers list <pgsql-hackers@postgresql.org>
> Subject: Re: [HACKERS] ALTER INDEX OWNER TO
>
> ohp@pyrenet.fr writes:
> > It seems that ALTER INDEX foo OWNER TO bar; doesn't work anymore.
> > The error is foo is not a table or a view.
>
> Yeah, I suppressed that alternative a few weeks ago, thinking that it
> was not sensible since we don't really support having indexes owned
> by anyone except the owner of the parent table.  Not sure what to do
> about the fact that pg_dump has been emitting it though. Maybe reduce
> the error to a warning, and make it a no-op?
>
>             regards, tom lane
>
>

-- 
Olivier PRENANT                    Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges                +33-5-61-50-97-01 (Fax)
31190 AUTERIVE                       +33-6-07-63-80-64 (GSM)
FRANCE                          Email: ohp@pyrenet.fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: obtaining row locking information
Next
From: Tom Lane
Date:
Subject: Re: obtaining row locking information