| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Renaming of pg_xlog and pg_clog |
| Date: | 2016-08-26 10:44:46 |
| Message-ID: | 20160826104446.n3cif4m7modslkrs@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: Fujii Masao 2016-08-26 <CAHGQGwHK2yimfLvG_WQ1Vrq2h+CMzgv5u6OEmxr-cbJRO+WKWQ(at)mail(dot)gmail(dot)com>
> > I agree on a hard break, unless we get pushback from users, and even
> > then, they can create the symlinks themselves.
>
> I strongly prefer symlink approach not to break many existing tools
> and scripts.
Symlinks might actually be worse than removing the directories
altogether. If your backup tool fails because the pg_xlog directory is
gone, you'll hopefully notice, but if you end up with a backup that
consists merely of a copy of a symlink named pg_xlog, you might not
notice.
Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2016-08-26 10:48:09 | Re: Renaming of pg_xlog and pg_clog |
| Previous Message | Heikki Linnakangas | 2016-08-26 09:53:21 | Re: Simplifying the interface of UpdateMinRecoveryPoint |