--On Mittwoch, November 05, 2008 19:20:07 -0500 Tom Lane
<[EMAIL PROTECTED]> wrote:
No, I think that should just be a no-op. We don't for instance throw
error when you ALTER OWNER to the existing owner.
Hmm okay. When looking at this i was remembering the discussion we had for
SET SCHEMA a long time ago, which indeed throws an error message:
ALTER TABLE foo SET SCHEMA public;
ERROR: relation "foo" is already in schema "public"
--
Thanks
Bernd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
