Re: Should pg_stat_bgwriter.buffers_backend_fsync be removed?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should pg_stat_bgwriter.buffers_backend_fsync be removed?
Date: 2014-04-29 13:30:08
Message-ID: 15740.1398778208@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Overall, I don't see much reason to tinker with this. If we had no
> reporting at all of this condition now, I'd probably be mildly more
> supportive of adding a log message than a counter. But since we've
> already got something and there's no real problem with it, I'm
> disinclined to make a change.

+1 ... if it ain't broke, why fix it?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Keith Fiske 2014-04-29 14:29:37 Re: pg_dump --pretty-print-views
Previous Message Robert Haas 2014-04-29 13:24:30 Re: Should pg_stat_bgwriter.buffers_backend_fsync be removed?