Horton

Re: Range Types - typo + NULL string constructor

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jeff Davis <pgsql@j-davis.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Alexander Korotkov <aekorotkov@gmail.com>, pgsql-hackers@postgresql.org
Date: 2011-10-26T17:28:52Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Replace the "New Linear" GiST split algorithm for boxes and points with a

Robert Haas <robertmhaas@gmail.com> writes:
> I believe that we're in trouble with XIDs as soon as you have two
> active XIDs that are separated by a billion, because then you could
> have a situation where some people think a given XID is in the future
> and others think it's in the past.  I have been wondering if we should
> have some sort of active guard against that scenario; I don't think we
> do at present.

Sure we do.  It's covered by the XID wraparound prevention logic.

			regards, tom lane