Re: BUG #14357: BUG : old_snapshot_threshold no effect

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: digoal(at)126(dot)com
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14357: BUG : old_snapshot_threshold no effect
Date: 2016-10-05 20:12:24
Message-ID: CACjxUsOUPjG3zYKX_R56_7+=jCQQ++CBtoB1yN0v3HtzAJiWwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Oct 5, 2016 at 11:21 AM, <digoal(at)126(dot)com> wrote:

> I set old_snapshot_threshold to 1min, but it's no effect to prevent bloat?

> BEGIN
> postgres=# insert into test01 values (1);
> INSERT 0 1
> [no COMMIT or ROLLBACK of this transaction]

> another session :
> [other modifications and vacuums]
> [no early cleanup or "snapshot too old" error]

> why ? It's a bug?

This feature does not attempt to perform early cleanup on (or past)
a transaction which has acquired a transaction ID (normally through
data modification) and which has not completed. In other words, it
helps with long-running read-only transactions, but a long-running
transaction which writes can still cause bloat.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Reyes Ponce 2016-10-06 02:34:14 Re: BUG #14343: UPSERT (ON CONFLICT) doesn't check ON CONFLICT constraint first
Previous Message digoal 2016-10-05 16:21:40 BUG #14357: BUG : old_snapshot_threshold no effect