> 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
