> Tom Lane wrote:

> > None of your use-cases require tracking multiple sets of stats within a
> > transaction, so I don't see why bother with that when we can just add a
> > "flush the stats" call.

FWIW I'm thinking that the corresponding code for handling the backends'
stats could be simplified, removing the hack that stores it in
TopTransactionContext, and just having a call to the stats flush
function in AbortTransaction and CommitTransaction.

Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Reply via email to