Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id 37D7719713C4;
	Tue,  6 Dec 2011 11:17:28 -0400 (AST)
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1RXwlr-0007BR-Jr; Tue, 06 Dec 2011 15:17:28 +0000
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id pB6FHD6i020006;
	Tue, 6 Dec 2011 10:17:13 -0500 (EST)
To: Magnus Hagander <magnus@hagander.net>
cc: Andrew Dunstan <andrew@dunslane.net>, Bruce Momjian <bruce@momjian.us>,
	PostgreSQL-documentation <pgsql-docs@postgresql.org>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Moving tablespaces 
In-reply-to: 
 <CABUevEy9MurQp23B0Z7r3jqDoW4N4BHPwnTgiNqNFY3jAJbFEg@mail.gmail.com>
References: 
 <CABUevEx2xYV==WRxWdMr=mS3Q1orBUvJcXa8AZx_LVbL122g5Q@mail.gmail.com>
	<201112041612.pB4GCHt06225@momjian.us>
	<CABUevEzuRQLddyY2yypiZpjWzzEzz0p66TgzoXGuz+jLxKgdkg@mail.gmail.com>
	<23636.1323016890@sss.pgh.pa.us> <4EDBA60D.2050904@dunslane.net>
	<26148.1323018451@sss.pgh.pa.us>
	<CABUevEyP-20VSpgBP9J16=vk9-fxj8O6KPr63r9jQxHoca9JeA@mail.gmail.com>
	<19894.1323184352@sss.pgh.pa.us>
	<CABUevEy9MurQp23B0Z7r3jqDoW4N4BHPwnTgiNqNFY3jAJbFEg@mail.gmail.com>
Comments: In-reply-to Magnus Hagander <magnus@hagander.net>
	message dated "Tue, 06 Dec 2011 16:13:46 +0100"
Date: Tue, 06 Dec 2011 10:17:13 -0500
Message-ID: <20005.1323184633@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Pg-Spam-Score: -3.1 (---)
X-Archive-Number: 201112/20
X-Sequence-Number: 7127

Magnus Hagander <magnus@hagander.net> writes:
> Throwing an error seems a lot more safe in this case than just
> returning NULL. Since it's a situtation that really shouldn't happen.
> Maybe an assert, but I think a regular ereport(ERROR) would be the
> best.

Not an assert, since it's trivially user-triggerable.

			regards, tom lane