Re: Patch for ALTER DATABASE WITH TABLESPACE

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch for ALTER DATABASE WITH TABLESPACE
Date: 2008-11-06 01:09:07
Message-ID: 9C21F1B80A3B0E932566CF1E@imhotep.credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--On Mittwoch, November 05, 2008 19:20:07 -0500 Tom Lane
<tgl(at)sss(dot)pgh(dot)pa(dot)us> 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tim Keitt 2008-11-06 01:31:57 pointer scope and memory contexts
Previous Message Tom Lane 2008-11-06 00:39:58 Inefficiency in InitIndexFreeSpaceMap