Re: Using xmin to identify last modified rows - Mailing list pgsql-general

From Richard Broersma
Subject Re: Using xmin to identify last modified rows
Date
Msg-id 396486430902250540g58da7123i19dcd7b620e21e6@mail.gmail.com
Whole thread Raw
In response to Re: Using xmin to identify last modified rows  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Using xmin to identify last modified rows  (Gregory Stark <stark@enterprisedb.com>)
Re: Using xmin to identify last modified rows  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Wed, Feb 25, 2009 at 5:21 AM, Gregory Stark <stark@enterprisedb.com> wrote:

> I'm not sure using xmin is such a great idea really. It's handy for ad-hoc
> queries but there are all kinds of cases where it might not give you the
> results you expect.


Its been a while since the following emails were written.  Has the
treatment of xmin changed since then, or is using a timestamp a better
practice?

http://archives.postgresql.org/pgsql-novice/2007-02/msg00079.php
http://archives.postgresql.org/pgsql-hackers/2004-02/msg00654.php

--
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

pgsql-general by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Using xmin to identify last modified rows
Next
From: Thom Brown
Date:
Subject: Re: Warm standby failover mechanism