Re: pg_archivecleanup bug

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_archivecleanup bug
Date: 2014-03-18 16:02:49
Message-ID: CA+U5nMKsz21Tmk7Ua1GViUw_NRJGb=WmqwTTrkv++VrO3S-Bkw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18 March 2014 15:50, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Mar 18, 2014 at 11:36 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> Given the above, this means we've run for about 7 years without a
>> reported issue on this. If we are going to "make this better" by
>> actually having it throw errors in places that didn't throw errors
>> before, are we sure that is going to make people happier? The archive
>> cleanup isn't exactly critical in most cases, so dynamic errors don't
>> matter much.
>
> We report errors returned by system calls in many other places. I
> can't see why this place should be any different.

Sure. Just wanted to make sure it's a conscious, explicit choice to do so.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2014-03-18 16:03:55 Re: Minimum supported version of Python?
Previous Message Peter Eisentraut 2014-03-18 16:02:14 Re: Minimum supported version of Python?