| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: tablespaces inside $PGDATA considered harmful |
| Date: | 2015-01-30 16:19:28 |
| Message-ID: | 20150130161928.GB20744@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 30, 2015 at 11:12:43AM -0500, Robert Haas wrote:
> I think everyone who has read this mailing list for a while is
> probably already aware of this problem. When you create a tablespace
> somewhere inside the data directory, weird things happen. If you
> pg_upgrade and then incautiously run the delete_old_cluster.sh script
> thus created, you will blow away large chunks of your data.[1] If you
pg_upgrade doesn't create the deletion script in this case, and warns
the user:
Could not create a script to delete the old cluster's data
files because user-defined tablespaces exist in the old cluster
directory. The old cluster's contents must be deleted manually.
> In the short term, I favor just adding a warning, so that people get
> some clue that they are doing something that might be a bad idea. In
> the long term, we might want to do more. Thoughts?
Yes, good idea.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sawada Masahiko | 2015-01-30 16:40:37 | Re: Proposal: knowing detail of config files via SQL |
| Previous Message | Robert Haas | 2015-01-30 16:12:43 | tablespaces inside $PGDATA considered harmful |