Re: Any reason to have heap_(de)formtuple?

From: Kris Jurka <books(at)ejurka(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Any reason to have heap_(de)formtuple?
Date: 2008-10-27 23:56:26
Message-ID: Pine.BSO.4.64.0810271955030.28764@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 23 Oct 2008, Kris Jurka wrote:

> The problem with trying to deprecate it is that the vast majority of the
> backend is still using the old interfaces, so people looking for
> inspiration for their external modules will likely end up using the old
> interface. Like Alvaro I started this conversion a while ago, got
> bored, and forgot about it. If people do want this conversion done while
> keeping the old interface around, I can track down that patch, update it
> and finish it up for the next CommitFest.
>

Here's a patch that changes everything over to the the new API and
implements the old API by calling the new API.

Kris Jurka

Attachment Content-Type Size
use-new-heaptuple-api.patch.gz application/octet-stream 28.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-10-28 00:35:52 Re: Re: [COMMITTERS] pgsql: Rework subtransaction commit protocol for hot standby.
Previous Message Tom Lane 2008-10-27 23:31:18 Re: Visibility map, partial vacuums