Re: Per-table freeze limit proposal

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Jim Buttafuoco <jim(at)contactbda(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Per-table freeze limit proposal
Date: 2005-09-19 15:05:16
Message-ID: 20050919150516.GY7630@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

It would also be very handy to be able to tell how many transactions (or
inserts/updates/deletes) have occured since the last vacuum. Presumably
autovacuum needs to know this already, but is it exposed?

On Thu, Sep 15, 2005 at 07:46:26AM -0400, Jim Buttafuoco wrote:
> while you are at it, can you put in some audit timestamps as to when the vacuum occurred (full vs not full).
>
>
> ---------- Original Message -----------
> From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
> To: Hackers <pgsql-hackers(at)postgresql(dot)org>
> Sent: Wed, 14 Sep 2005 22:14:23 -0400
> Subject: [HACKERS] Per-table freeze limit proposal
>
> > Hackers,
> >
> > As you've probably heard too many times already, I'm thinking in
> > improving vacuum, so we can keep track of the freeze Xid on a table
> > level, rather than database level. Hopefully this will eliminate the
> > need for database-wide vacuums.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-09-19 15:09:12 Re: DISTINCT vs. GROUP BY
Previous Message Tom Lane 2005-09-19 15:01:33 Re: Start translating

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2005-09-19 17:50:22 Re: statement logging / extended query protocol issues
Previous Message Tom Lane 2005-09-18 04:04:21 Re: doc/FAQ_DEV: about profile