Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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: use-new-heaptuple-api.patch.gz
Description: application/octet-stream (28.0 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2008-10-28 00:35:52
Subject: Re: Re: [COMMITTERS] pgsql: Rework subtransaction commitprotocol for hot standby.
Previous:From: Tom LaneDate: 2008-10-27 23:31:18
Subject: Re: Visibility map, partial vacuums

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group