| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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 19:57:42 |
| Message-ID: | 20150423195742.GK3055@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-04-23 15:46:20 -0400, Robert Haas wrote:
> Well, we've made backward-incompatible changes before. Not to this
> specific thing, but in general. I don't think there's anything
> preventing us from doing so here, except that we don't want to annoy
> too many users.
I think the number of users that have done this, and haven't yet
(knowing or unknowningly) been bitten by it is pretty low. In that
scenario it seems much better to break compatibility given that it's
pretty easy to fix during restore (just precreate the tablespace). It's
not something you have to retest a whole application for.
If you want to avoid that one error you can still do pg_dumpall
--globals, edit and run that script, and only then restore the the
actual databases.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2015-04-23 20:04:35 | Re: pg_dump: largeobject behavior issues (possible bug) |
| Previous Message | Andres Freund | 2015-04-23 19:53:50 | Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0 |