| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tim Lewis <Tim(dot)Lewis(at)vialect(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Ben Lancaster <benlancaster(at)holler(dot)co(dot)uk>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_archivecleanup with multiple slaves |
| Date: | 2011-05-22 22:06:59 |
| Message-ID: | BANLkTincapSdDmrGAY6rCh0kwb5we3kVUA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, May 20, 2011 at 4:58 PM, Tim Lewis <Tim(dot)Lewis(at)vialect(dot)com> wrote:
> I don't actually use streaming replication, but what exactly is the problem
> with the hard link for each slave solution, and the slaves handling there
> own pg_archivecleanup?
Doing so creates a single point of failure.
We had problems with links in earlier versions, so we learned the hard
way to stay clear of them.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Diego Fernández Slezak | 2011-05-22 22:24:26 | Re: ERROR: could not read block |
| Previous Message | Craig James | 2011-05-22 01:27:47 | Re: Who is causing all this i/o? |