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
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
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
: 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
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
