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

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Any reason to have heap_(de)formtuple?
Date: 2008-10-23 15:17:00
Message-ID: 4900956C.7020704@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera napsal(a):
> Zdenek Kotala wrote:
>> Tom Lane napsal(a):
>
>>> 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 ...
>> What's about convert null array to boolean and call heap_form_tuple?
>
> Agreed, I started doing that some time ago ... it doesn't seem all that
> complicated.

Do you have any half patch?

> We could try to add a #warning if an external module uses
> the deprecated interface, for a couple of releases, and then perhaps
> drop it.

+1

Zdenek

--
Zdenek Kotala Sun Microsystems
Prague, Czech Republic http://sun.com/postgresql

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-10-23 15:21:39 patch: Client certificate requirements
Previous Message Alvaro Herrera 2008-10-23 15:14:12 Re: Any reason to have heap_(de)formtuple?