-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 03 Apr 2008 21:26:46 -0400
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
> > I would agree with this. We would need a history of checkpoints that
> > didn't reset until we told it to.
>
> Indeed, but the submitted patch has nought whatsoever to do with that.
> It exposes some instantaneous state.
>
> You could perhaps *build* a log facility on top of that, at the SQL
> level; but I don't see the point, and I definitely disagree that it
> would be "easier than trolling the logs".
Having the ability to do this:
SELECT * FROM pg_stat_bgwriter
WHERE last_checkpoint
BETWEEN (current_time - '1 Day'::interval) AND current_time;
Would be very useful. Which I can do with logs currently. You are
correct. However from a usability, remote reporting and manageability
perspective it certainly is not the same as something as I describe
above.
Note I am perfectly willing to table this until we have a full todo and
specification for a feature.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFH9YVlATb/zqfZUUQRAnRxAKCab3O4dmBXctXTptDFwkRx+1zUQQCdFmsN
E3GWNoC90jS7ooFgArR8Nv0=
=CvMx
-----END PGP SIGNATURE-----
