| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(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 15:50:42 |
| Message-ID: | CA+Tgmob0GRDePNpv65EXxkBZKY8sKsxGFGPC=wBGo6GriX09WA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2014-03-18 15:59:06 | Re: Patch: show relation and tuple infos of a lock to acquire |
| Previous Message | Peter Eisentraut | 2014-03-18 15:49:24 | Re: Minimum supported version of Python? |