| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Tablespaces in the data directory |
| Date: | 2012-12-04 21:47:08 |
| Message-ID: | 50BE6F5C.3090003@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2012-12-01 14:45, Magnus Hagander wrote:
> Someone just reported a problem when they had created a new tablespace
> inside the old data directory. I'm sure there can be other issues
> caused by this as well, but this is mainly a confusing scenario for
> people now.
>
> As there isn't (as far as I know at least) any actual *point* in
> creating a tablespace inside the main data directory, should we
> perhaps disallow this in CREATE TABLESPACE? Or at least throw a
> WARNING if one does it?
Does this apply when creating a tablespace in another tablespace too? If
the problem is that pg_basebackup copies that data twice it sounds like
it should.
--
Andreas Karlsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2012-12-04 21:56:19 | Re: WIP: store additional info in GIN index |
| Previous Message | Asif Rehman | 2012-12-04 21:04:11 | Re: why can't plpgsql return a row-expression? |