On 3/14/19 11:45 AM, Perumal Raj wrote:
Please reply to list also.
Ccing list.
Thanks Adrian for the reply,
Yes , i went through the document.
My Only Worry is , Will i hit performance issue once i reach 200M
Age(default) even i have only static table.
If is truly static then there will be
On 3/11/19 1:24 PM, Perumal Raj wrote:
Hi Adrian
What was the full message?
autovacuum: VACUUM (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 transactio
Hi Adrian
What was the full message?
autovacuum: VACUUM (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
On 3/11/19 12:16 PM, Perumal Raj wrote:
Hi Adrian/Joshua
Sorry to mention in the previous thread,
Auto-vacuum is already enabled in the Cluster and its doing the job
perfectly. But only thing manual vacuum scheduled now (weekly Cluster
wide) after noticing 'Transaction Wraparound message duri
Hi Adrian/Joshua
Sorry to mention in the previous thread,
Auto-vacuum is already enabled in the Cluster and its doing the job
perfectly. But only thing manual vacuum scheduled now (weekly Cluster wide)
after noticing 'Transaction Wraparound message during Autovacuum run.
Version : 9.2.24
Query
On 3/11/19 11:51 AM, Perumal Raj wrote:
Hi Experts
I have noticed in my Database that, there is no regular Vacuum
maintenance happening
What Postgres version?
So i started Weekly Job across cluster. But still i am seeing gradual
growth on transacation ID.
What query are you using?
DB i
Hi Experts
I have noticed in my Database that, there is no regular Vacuum maintenance
happening
So i started Weekly Job across cluster. But still i am seeing gradual
growth on transacation ID.
DB is still using default autovacuum_freeze_min_age &
autovacuum_freeze_table_age.
Question : Since i a
