Tom Lane wrote: > Bruce Momjian <pgman@candle.pha.pa.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@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
