From: | ohp(at)pyrenet(dot)fr |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER INDEX OWNER TO |
Date: | 2005-08-15 14:58:30 |
Message-ID: | Pine.UW2.4.53.0508151657110.12006@sun.pyrenet |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us>
> To: ohp(at)pyrenet(dot)fr
> Cc: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
> Subject: Re: [HACKERS] ALTER INDEX OWNER TO
>
> ohp(at)pyrenet(dot)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(at)pyrenet(dot)fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroki Kataoka | 2005-08-15 16:12:05 | Re: Changes improve the performance of INSERT and UPDATE |
Previous Message | Tom Lane | 2005-08-15 14:57:13 | Re: obtaining row locking information |