Re: [HACKERS] ALTER INDEX OWNER TO
Where are we on this? --- Christopher Kings-Lynne wrote: 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? Hmmm I so don't remember having pg_dump issue that - but I guess I must have... Chris ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[HACKERS] ALTER INDEX OWNER TO
Hi all, It seems that ALTER INDEX foo OWNER TO bar; doesn't work anymore. The error is foo is not a table or a view. That's not a problem per se, but pg_dump continues to issue those commands. This is since a few weeks on CVS. Regards -- 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) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
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 ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] ALTER INDEX OWNER TO
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 [EMAIL PROTECTED] 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) ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] ALTER INDEX OWNER TO
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? Hmmm I so don't remember having pg_dump issue that - but I guess I must have... Chris ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
