Re: Improvement of procArray.xmin for VACUUM - Mailing list pgsql-patches

From Gregory Stark
Subject Re: Improvement of procArray.xmin for VACUUM
Date
Msg-id 874poa62ki.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Improvement of procArray.xmin for VACUUM  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Improvement of procArray.xmin for VACUUM
List pgsql-patches
> OTOH, do we have any evidence that this is worth bothering with at all?
> I fear that the cases of long-running transactions that are problems
> in the real world wouldn't be helped much --- for instance, pg_dump
> wouldn't change behavior because it uses a serializable transaction.
Well I think this would be the same infrastructure we would need to do the
other discussed improvement to address pg_dump's impact. That would require us
to publish the youngest xmax of the live snapshots. Vacuum could deduce that
that xid cannot possibly see any transactions between the youngest extant xmax
and the oldest in-progress transaction.
--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com


pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #3095: LDAP authentication parsing incorrectly
Next
From: Gregory Stark
Date:
Subject: Re: LIMIT/SORT optimization