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+TgmoZ8byYDu+Cqf_s7aEhFtdd4_=OXGR0kO1LdmjcVF8Kw_Q@mail.gmail.com
Whole thread Raw
In response to Re: Learning to hack Postgres - Keeping track of ctids  (Emrul <emrul@emrul.com>)
List pgsql-hackers
On Mon, Oct 3, 2016 at 4:30 PM, Emrul <emrul@emrul.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



pgsql-hackers by date:

Previous
From: Emrul
Date:
Subject: Re: Learning to hack Postgres - Keeping track of ctids
Next
From: Robert Haas
Date:
Subject: Re: asynchronous execution