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-23 19:59:56
Message-ID: Pine.BSO.4.64.0810231554590.9238@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 23 Oct 2008, Tom Lane wrote:

> Well, aside from the gruntwork needed to convert all the core code that
> still uses the old APIs, there's the prospect of breaking extension
> modules that still use the old APIs. It's kind of annoying to have two
> copies of that code, but less annoying than removing it would be ...
>

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.

Kris Jurka

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-10-23 20:23:16 Re: SSL cleanups/hostname verification
Previous Message Simon Riggs 2008-10-23 18:37:35 Re: Re: [COMMITTERS] pgsql: Rework subtransaction commit protocol for hot standby.