From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Perumal Raj <perucinci(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Autovacuum Transaction Wraparound |
Date: | 2019-03-13 19:23:31 |
Message-ID: | 6616bb40-9b76-a786-7276-ff1e2a9cd03b@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/11/19 1:24 PM, Perumal Raj wrote:
> Hi Adrian
>
> What was the full message?
>
> autovacuum: VACUUM <table name >(to prevent wraparound)
>
> Though i am running vacuum manually (nowadays) and autovacuum is running
> perfectly once its threshold reaches.
>
> What will happen if my DB reaches 200M transaction age again ? ( Here my
> understanding is no dead tuples to cleanup --- I may be missing full
> concept , Please correct me if i am wrong) .
>
> What will be impact to DB ( Performance ) During Vacuum freeze ( My
> Assumption is autovacuum will run "vacuum freeze" once DB age reached
> 200M ) ?
I would read this:
https://www.postgresql.org/docs/9.2/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND
I believe it will answer most of your questions.
>
> When should i consider to increase pg_settings value with respect to
> Autovacuum ?
>
> Regards,
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Benedict Holland | 2019-03-13 20:47:35 | Re: Where to store Blobs? |
Previous Message | Vijaykumar Jain | 2019-03-13 18:35:02 | Re: [External] Re: xmin and very high number of concurrent transactions |