On Tue, Feb 14, 2017 at 11:49 AM, Seki, Eiji <seki.e...@jp.fujitsu.com> wrote: > Hi all, > > I propose the patch that adds a function GetOldestXminExtended that is like > GetOldestXmin but can ignore arbitrary vacuum flags. And then, rewrite > GetOldestXmin to use it. Note that this is done so as not to change the > behavior of GetOldestXmin. > > This change will be useful for features that only reads rows that are visible > by all transactions and could not wait specific processes (VACUUM, ANALYZE, > etc...) for performance. >
How will you decide just based on oldest xmin whether the tuple is visible or not? How will you take decisions about tuples which have xmax set? -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
