| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)berkus(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Petr Jelinek <petr(at)2ndquadrant(dot)com> |
| Subject: | Re: Notes on testing Postgres 10b1 |
| Date: | 2017-06-08 01:37:02 |
| Message-ID: | bf31916c-ed0b-60b4-036f-9600b0e32429@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/7/17 21:19, Josh Berkus wrote:
> The user's first thought is going to be a network issue, or a bug, or
> some other problem, not a missing PK. Yeah, they can find that
> information in the logs, but only if they think to look for it in the
> first place, and in some environments (AWS, containers, etc.) logs can
> be very hard to access.
You're not going to get very far with using this feature if you are not
looking in the logs for errors. These are asynchronously operating
background workers, so the only way they can communicate problems is
through the log.
I don't disagree with your general premise. We have done a fair amount
of fiddling already to show some errors as early as possible. But we
can't know all of them, and we shouldn't give the impression that we do.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2017-06-08 01:42:30 | Re: TAP: allow overriding PostgresNode in get_new_node |
| Previous Message | Petr Jelinek | 2017-06-08 01:25:51 | Re: Notes on testing Postgres 10b1 |