Re: Using stats_command_string for xact statistics

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Using stats_command_string for xact statistics
Date: 2006-02-14 02:03:22
Message-ID: 200602140203.k1E23Mn16977@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I know we said we don't want to add an additional GUC variable just to
> > control xact statistics, but I am thinking that using
> > stat_command_string isn't a logical variable to use because it is
> > unrelated to commutative statistics.
>
> > I am thinking using row and block-level statistics to turn on xact
> > statistics makes sense, but not to use stat_command_string for that
> > purpose.
>
> I don't see any strong logic to that, and changing the behavior just
> for the sake of change doesn't appeal to me...

OK, additional sentence added, and paragraph split into two:

! Additionally, per-database transaction commit and abort statistics
! are collected if any of these parameters are set.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bricklen Anderson 2006-02-14 02:44:28 Re: Anyone want to admit to being presinet.com?
Previous Message Darcy Buskermolen 2006-02-14 02:03:08 Re: Anyone want to admit to being presinet.com?

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Klosterman 2006-02-14 02:10:13 Re: BUG #2246: Bad malloc interactions: ecpg, openssl
Previous Message Stephen Frost 2006-02-14 02:02:59 Re: BUG #2246: Bad malloc interactions: ecpg, openssl