From: | Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com> |
---|---|
To: | Emrul <emrul(at)emrul(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Learning to hack Postgres - Keeping track of ctids |
Date: | 2016-09-30 12:03:32 |
Message-ID: | CAMsr+YFRYXpB8cV+V3TLhAYhn=RQB0KmvMhwjOVdBpCP8itkrQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 30 Sep. 2016 19:36, "Emrul" <emrul(at)emrul(dot)com> wrote:
>
> Thanks Craig, I will look at that code.
>
> The alternative I'm considering is whether I can define my own index type
on
> the column storing my array of primary key ids. The index would, for each
> primary key id just provide a reference to the ctids of the related
records.
>
> In theory, I think this might be less work. However, I am yet to find a
> simple/bare index implementation that I can build upon.
I don't think indexes are fully pluggable yet. And I'd be surprised if it
were possible within GiST /GIN. Check out the 9.6 / v10 pg_am changes,
which I think may be relevant.
Or it could be an unrelated dead end because I know little about indexing.
>
>
>
> --
> View this message in context:
http://postgresql.nabble.com/Learning-to-hack-Postgres-Keeping-track-of-ctids-tp5923649p5923757.html
> Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2016-09-30 12:15:39 | [PATCH] Refactoring: rename md5Salt to pwsalt |
Previous Message | Jeevan Chalke | 2016-09-30 11:58:43 | Re: Aggregate Push Down - Performing aggregation on foreign server |