| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Jan Wieck <janwieck(at)yahoo(dot)com> |
| Cc: | Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Exposing the Xact commit order to the user |
| Date: | 2010-06-04 16:52:49 |
| Message-ID: | 1275670221-sup-2744@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Jan Wieck's message of jue jun 03 19:52:19 -0400 2010:
> On 6/3/2010 7:11 PM, Alvaro Herrera wrote:
> > Why not send separate numbers of tuple inserts/updates/deletes, which we
> > already have from pgstats?
>
> We only have them for the entire database. The purpose of this is just a
> guesstimate about what data volume to expect if I were to select all log
> from a particular transaction.
But we already have per table counters. Couldn't we aggregate them per
transaction as well, if this feature is enabled? I'm guessing that this
is going to have some uses besides Slony; vague measurements could turn
out to be unusable for some of these.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-06-04 17:20:15 | Re: Idea for getting rid of VACUUM FREEZE on cold pages |
| Previous Message | Marc Munro | 2010-06-04 16:49:22 | Re: [PATCH] Fix leaky VIEWs for RLS |