Re: Per-table freeze limit proposal
От | Jim C. Nasby |
---|---|
Тема | Re: Per-table freeze limit proposal |
Дата | |
Msg-id | 20050919150516.GY7630@pervasive.com обсуждение исходный текст |
Ответ на | Re: Per-table freeze limit proposal ("Jim Buttafuoco" <jim@contactbda.com>) |
Список | pgsql-hackers |
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@alvh.no-ip.org> > To: Hackers <pgsql-hackers@postgresql.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@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
В списке pgsql-hackers по дате отправления: