Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 0A85119713C4; Tue, 6 Dec 2011 11:12:50 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RXwhK-00072T-Fj; Tue, 06 Dec 2011 15:12:50 +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 pB6FCW5N019896; Tue, 6 Dec 2011 10:12:32 -0500 (EST) To: Magnus Hagander cc: Andrew Dunstan , Bruce Momjian , PostgreSQL-documentation , PostgreSQL-development Subject: Re: [HACKERS] Moving tablespaces In-reply-to: References: <201112041612.pB4GCHt06225@momjian.us> <23636.1323016890@sss.pgh.pa.us> <4EDBA60D.2050904@dunslane.net> <26148.1323018451@sss.pgh.pa.us> Comments: In-reply-to Magnus Hagander message dated "Tue, 06 Dec 2011 15:59:11 +0100" Date: Tue, 06 Dec 2011 10:12:32 -0500 Message-ID: <19894.1323184352@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -3.1 (---) X-Archive-Number: 201112/18 X-Sequence-Number: 7125 Magnus Hagander writes: > AFAICT, it should be as simple as the attached. Oh, one other thought is that the function body has to be conditionalized on HAVE_READLINK (the fact that you forgot that somewhere else isn't an excuse for not doing it here). IIRC, only the two built-in tablespaces can exist when not HAVE_READLINK, so it seems sufficient to handle those cases and then PG_RETURN_NULL (or maybe throw error) when not HAVE_READLINK. regards, tom lane