Re: pg_archivecleanup bug - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_archivecleanup bug
Date
Msg-id CA+Tgmob0GRDePNpv65EXxkBZKY8sKsxGFGPC=wBGo6GriX09WA@mail.gmail.com
Whole thread Raw
In response to Re: pg_archivecleanup bug  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: pg_archivecleanup bug  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Tue, Mar 18, 2014 at 11:36 AM, Simon Riggs <simon@2ndquadrant.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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Minimum supported version of Python?
Next
From: Greg Stark
Date:
Subject: Re: Patch: show relation and tuple infos of a lock to acquire