| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Martin Zaun <Martin(dot)Zaun(at)Sun(dot)COM>, Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, List pgsql-patches <pgsql-patches(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] odd output in restore mode |
| Date: | 2008-07-25 20:58:57 |
| Message-ID: | 792.1217019537@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> On Fri, 2008-07-25 at 16:31 -0400, Tom Lane wrote:
>> I thought the latest conclusion was that changing the behavior of
>> pg_standby itself wouldn't address the problem anyway, and that what we
>> need is just a docs patch recommending that people use safe copying
>> methods in their scripts that copy to the archive area?
> Plus the rest of this patch, which is really very simple.
Why? AFAICT the patch is just a kluge that adds user-visible complexity
without providing a solution that's actually sure to work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | daveg | 2008-07-25 21:11:02 | Re: Adding WHERE clause to pg_dump |
| Previous Message | Simon Riggs | 2008-07-25 20:53:02 | Re: [PATCHES] odd output in restore mode |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-07-25 21:25:01 | Re: [PATCHES] odd output in restore mode |
| Previous Message | Simon Riggs | 2008-07-25 20:53:02 | Re: [PATCHES] odd output in restore mode |