From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(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:14:12 |
Message-ID: | 20081023151412.GA4845@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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. 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.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Zdenek Kotala | 2008-10-23 15:17:00 | Re: Any reason to have heap_(de)formtuple? |
Previous Message | Tom Lane | 2008-10-23 15:14:06 | Re: Any reason to have heap_(de)formtuple? |