| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location |
| Date: | 2016-04-14 18:55:37 |
| Message-ID: | CA+TgmoYB40DZ5uCYGVG5w8kUV5YwOTEW7kdcCNpory+9WgTVuA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 14, 2016 at 11:12 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2016-04-14 13:43:34 +0530, Ashutosh Sharma wrote:
>> I tried performing pg_basebackup after creating a symbolic link for
>> pg_replslot, pg_stat_tmp, pg_log and pg_clog in the source directory
>
> That's not supported, and I strongly suspect that you're goint to hit
> more than just this issue. The only directory you're allowed to symlink
> away is pg_xlog.
I think various tools might choke on such a configuration, but I'm not
entirely sure why we haven't made them all work. Is there some more
fundamental problem?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-04-14 19:01:16 | Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location |
| Previous Message | Magnus Hagander | 2016-04-14 18:48:18 | Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location |