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

Поиск
Список
Период
Сортировка
От Kris Jurka
Тема Re: Any reason to have heap_(de)formtuple?
Дата
Msg-id Pine.BSO.4.64.0810231554590.9238@leary.csoft.net
обсуждение исходный текст
Ответ на Re: Any reason to have heap_(de)formtuple?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Any reason to have heap_(de)formtuple?  (Greg Stark <greg.stark@enterprisedb.com>)
Re: Any reason to have heap_(de)formtuple?  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Re: Any reason to have heap_(de)formtuple?  (Kris Jurka <books@ejurka.com>)
Список 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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Rework subtransaction commit protocol for hot standby.
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: SSL cleanups/hostname verification