RE: PATCH: Postgresql Patch

Hi,

The problem with ctid is found from this URL
http://www.postgresql.org/docs/8.1/interactive/ddl-system-columns.html

"The physical location of the row version within its table. Note that
although the ctid can be used to locate the row version very quickly, a
row's ctid will change each time it is updated or moved by VACUUM FULL.
Therefore ctid is useless as a long-term row identifier. The OID, or even
better a user-defined serial number, should be used to identify logical
rows."

Therefore using ctids are risky as other deletes, updates, or vacuums may
have changed the internal ctid and so the only other option is to move away
from the deprecated OID to a sequential column.

Rgds

-----Original Message-----
From: Guillaume Cottenceau [mailto:[email protected]] 
Sent: 23 June 2008 05:58 PM
To: Stipe Tolj
Cc: Hillel; [email protected]
Subject: Re: PATCH: Postgresql Patch

Stipe Tolj <st 'at' tolj.org> writes:

> Hillel, can you please revise and update the patch?

AFAIK, the attached patch should work with all versions of pg (at least
since 7.3).