Re: Learning to hack Postgres - Keeping track of ctids - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Learning to hack Postgres - Keeping track of ctids
Date
Msg-id CA+TgmoaFThRF0bE3BfTWjrozc=7ADHO_xNFLh3E7F7wBLBMm-g@mail.gmail.com
Whole thread Raw
In response to Learning to hack Postgres - Keeping track of ctids  (Emrul <emrul@emrul.com>)
Responses Re: Learning to hack Postgres - Keeping track of ctids  (Emrul <emrul@emrul.com>)
List pgsql-hackers
On Thu, Sep 29, 2016 at 4:15 PM, Emrul <emrul@emrul.com> wrote:
> What I'd like to do is store a reference to all the links from one record
> using an array type that stores links to all related tables.
>
> At first, I've succeeded in doing this using primary key Ids and this works
> fine.  However, I'd like to be able to bypass the index lookup altogether by
> storing the ctids in my array instead of the primary key ids.

I suspect you're going to find that this is very difficult and doesn't
actually make anything any better than just using the primary key IDs.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Showing parallel status in \df+
Next
From: Robert Haas
Date:
Subject: Re: Question / requests.