| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump's aborted transactions |
| Date: | 2015-02-04 14:04:23 |
| Message-ID: | CA+TgmoacRQn+jiEN9ppt7RJ2sNsp7-VOvorQZoNojzkid7wtVA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 4, 2015 at 8:08 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Apologies for the confusion- the client isn't using it to determine if
> there's activity. They're using it exactly as it's intended, as I
> understand it- to check and see if the number of rollbacks is
> signifigant compared to the number of commits. The issue is that, with
> databases that have little activity, you can end up with a commit ratio
> of 50% or less. Perhaps check_postgres could have an option to only
> complain when some minimum number of transactions has been reached..
That sounds like a much better idea. pg_dump isn't really doing
anything wrong here, so "fixing" it feels like the wrong solution.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-02-04 14:48:38 | Re: Getting rid of wal_level=archive and default to hot_standby + wal_senders |
| Previous Message | Robert Haas | 2015-02-04 13:52:48 | Re: Unnecessary pointer-NULL checks in pgp-pgsql.c |