Re: Issue in autovacuum

From: "Agarwal, Prateek" <prateeka(at)hpe(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Issue in autovacuum
Date: 2017-03-30 06:59:24
Message-ID: TU4PR84MB02562A3EBDA7DC0D57258F47D5340@TU4PR84MB0256.NAMPRD84.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks for your responses!
We are not using prepared transactions and not using replication slots as well.
We do have a lot of transactions getting created and closed on account of executing the update queries.

Thanks,
Prateek
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, March 28, 2017 11:54 PM
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Agarwal, Prateek <prateeka(at)hpe(dot)com>; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Issue in autovacuum

Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 03/28/2017 03:15 AM, Agarwal, Prateek wrote:
>> When I upgrade my db to 9.4.6 (my application remains same and hardly
>> any code change w.r.t transaction declarations), it started
>> complaining about dead rows below. I am not sure if it is something
>> to do with upgrade or not.

> So are you using replication slots?

Or prepared transactions? Or maybe you just have a really old open transaction?

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Giuseppe Sacco 2017-03-30 07:25:20 Re: Using relations in the SELECT part
Previous Message harpagornis 2017-03-30 04:18:08 Re: Tablespace Default Behavior