Excerpts from Chris Browne's message of jue jun 03 16:21:35 -0400 2010: > What this offers is *SOME* idea of how much updating work a particular > transaction did. It's a bit worse than you suggest: > > - If replication triggers have captured tuples, those would get > counted. > > - TOAST updates might lead to extra updates being counted. > > But back to where you started, I'd anticipate 7 inserts, 7 deletes, > and 7 updates being counted as something around 21 updates. > > And if that included 5 TOAST changes, it might bump up to 26. > > If there were replication triggers in place, that might bump the count > up to 45 (which I chose arbitrarily).
Why not send separate numbers of tuple inserts/updates/deletes, which we already have from pgstats? -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
