| From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Stéphane A(dot) Schildknecht <stephane(dot)schildknecht(at)postgresqlfr(dot)org>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Using xmin to identify last modified rows |
| Date: | 2009-02-25 13:40:49 |
| Message-ID: | 396486430902250540g58da7123i19dcd7b620e21e6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Feb 25, 2009 at 5:21 AM, Gregory Stark <stark(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shahbaz A. Tyagi | 2009-02-25 13:54:04 | Re: Restore DB |
| Previous Message | Knut P. Lehre | 2009-02-25 13:29:36 | Several simultaneous libpq connections from the same application to different servers using different SSL certs |