Re: Any reason to have heap_(de)formtuple? - Mailing list pgsql-hackers

From Kris Jurka
Subject Re: Any reason to have heap_(de)formtuple?
Date
Msg-id Pine.BSO.4.64.0810271955030.28764@leary.csoft.net
Whole thread Raw
In response to Re: Any reason to have heap_(de)formtuple?  (Kris Jurka <books@ejurka.com>)
Responses Re: Any reason to have heap_(de)formtuple?
Re: Any reason to have heap_(de)formtuple?
List 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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Visibility map, partial vacuums
Next
From: Simon Riggs
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Rework subtransaction commit protocol for hot standby.