Add a pgstat config column to pg_database, so this, entire thing can be enabled/disabled on a per db basis

From: Euler Taveira de Oliveira <euler(at)timbira(dot)com>
To: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Add a pgstat config column to pg_database, so this, entire thing can be enabled/disabled on a per db basis
Date: 2009-10-20 02:11:58
Message-ID: 4ADD1C6E.3090605@timbira.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Looking at the code, it seems the $SUBJECT (comment) is obsolete. Indeed, we
can set it with 'ALTER DATABASE foo SET track_*'.

One thing that bothers me is the fact that if i turn it off, do a lot of stuff
and then turn it on my counters will be wrong. :( Maybe should we call
pgstat_reset_counters() in a new-function (assign_track_counts(?) that will be
in assign_hook for guc 'track_counts')?

--
Euler Taveira de Oliveira
http://www.timbira.com/

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2009-10-20 02:21:24 Re: per table random-page-cost?
Previous Message Tom Lane 2009-10-20 02:01:48 Re: Could postgres be much cleaner if a future release skipped backward compatibility?