From: Pallav Kalva <pkalva@livedatagroup.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: 8.2 Autovacuum BUG ?
Date: Fri, 31 Aug 2007 12:05:36 -0400
Message-ID: <46D83C50.3040409@livedatagroup.com> (raw)
In-Reply-To: <25038.1188574775@sss.pgh.pa.us>
References: <46D83427.60001@livedatagroup.com>
<25038.1188574775@sss.pgh.pa.us>
Tom Lane wrote:
> Pallav Kalva <pkalva@livedatagroup.com> writes:
>
>> We turned on autovacuums on 8.2 and we have a database which is read
>> only , it is basically a USPS database used only for address lookups
>> (only SELECTS, no updates/deletes/inserts).
>>
>
>
>> This database has about 10gig data and yesterday autovacuum started
>> on this database and all of a sudden I see lot of archive logs generated
>> during this time, I guess it might have generated close to 3-4gig data
>> during this period.
>>
>
> Probably represents freezing of old tuples, which is a WAL-logged
> operation as of 8.2. Is it likely that the data is 200M transactions
> old?
>
If nothing changed on these tables how can it freeze old tuples ?
Does it mean that once it reaches 200M transactions it will do the same
thing all over again ?
If I am doing just SELECTS on these tables ? how can there be any
transactions ? or SELECTS considered transactions too ?
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pkalva@livedatagroup.com, tgl@sss.pgh.pa.us
Subject: Re: 8.2 Autovacuum BUG ?
In-Reply-To: <46D83C50.3040409@livedatagroup.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox