| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Moving tablespaces |
| Date: | 2011-12-06 15:12:32 |
| Message-ID: | 19894.1323184352@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-12-06 15:13:46 | Re: [HACKERS] Moving tablespaces |
| Previous Message | Tom Lane | 2011-12-06 15:05:46 | Re: [HACKERS] Moving tablespaces |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-12-06 15:13:46 | Re: [HACKERS] Moving tablespaces |
| Previous Message | Tom Lane | 2011-12-06 15:05:46 | Re: [HACKERS] Moving tablespaces |