Re: Learning to hack Postgres - Keeping track of ctids

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Emrul <emrul(at)emrul(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Learning to hack Postgres - Keeping track of ctids
Date: 2016-10-03 20:26:32
Message-ID: CA+TgmoaFThRF0bE3BfTWjrozc=7ADHO_xNFLh3E7F7wBLBMm-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 29, 2016 at 4:15 PM, Emrul <emrul(at)emrul(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-10-03 20:27:51 Re: Question / requests.
Previous Message Pavel Stehule 2016-10-03 20:18:08 Re: Showing parallel status in \df+