From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Ilja Golshtein <ilejn(at)yandex(dot)ru>, mike(at)fuhr(dot)org |
Subject: | Re: ctid access is slow |
Date: | 2005-08-23 22:29:24 |
Message-ID: | 200508231829.24755.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tuesday 23 August 2005 15:55, Alvaro Herrera wrote:
> On Tue, Aug 23, 2005 at 06:02:05PM +0400, Ilja Golshtein wrote:
> > The only thing I am curios is ctid good for anything from user point
> > of view?
>
> No -- it changes far too frequently for that.
Oh I dunno... In general I'd agree with you, but I've seen a couple of (some
would say hackey) use cases where you use the ctid to iterate over the
columns returned in a row in a plpgsql function... :-)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Probert | 2005-08-23 23:36:01 | Re: [newbie] server startup |
Previous Message | Ron Mayer | 2005-08-23 21:48:50 | Re: ctid access is slow |