| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: tablespaces inside $PGDATA considered harmful |
| Date: | 2015-04-23 15:05:14 |
| Message-ID: | 20150423150514.GF3055@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-04-23 11:00:43 -0400, Bruce Momjian wrote:
> On Thu, Apr 23, 2015 at 09:13:52AM -0400, Robert Haas wrote:
> > I think this is a good thing to do, but I sure wish we could go
> > further and block it completely. That may require more thought than
> > we have time to put in at this stage of the release cycle, though, so
> > +1 for doing at least this much.
>
> OK, good. Thinking to 9.6, I am not sure how we could throw an error
> because we have allowed this in the past and pg_dump is going to be
> restored with a raw SQL CREATE TABLESPACE command.
We could just document that you need to pre-create the tablespace and
ignore the resulting error. This isn't going to affect too many people.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrízio de Royes Mello | 2015-04-23 15:05:53 | Re: Add CINE for ALTER TABLE ... ADD COLUMN |
| Previous Message | Jim Nasby | 2015-04-23 15:04:33 | Re: Freeze avoidance of very large table. |