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:34:09
Message-ID: CA+TgmoZ8byYDu+Cqf_s7aEhFtdd4_=OXGR0kO1LdmjcVF8Kw_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 3, 2016 at 4:30 PM, Emrul <emrul(at)emrul(dot)com> wrote:
> I suspect you're right. I've looked at the code and it will be very difficult
> (especially if I want to do it as an extension rather than patching
> Postgres) and with all the stuff I'd need to do to make it work you're also
> right that it probably won't improve upon just using primary key Ids.

Fortunately, primary keys are awesome, and are designed for exactly
the problem you're trying to solve, so that's OK. :-)

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-10-03 21:00:40 Re: asynchronous execution
Previous Message Emrul 2016-10-03 20:30:31 Re: Learning to hack Postgres - Keeping track of ctids