Re: Any reason to have heap_(de)formtuple?
От | Greg Stark |
---|---|
Тема | Re: Any reason to have heap_(de)formtuple? |
Дата | |
Msg-id | FCAE391C-741D-44B6-B765-4465388468D6@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: Any reason to have heap_(de)formtuple? (Kris Jurka <books@ejurka.com>) |
Список | pgsql-hackers |
The sad thing us that I also did a patch for this and lost it. I think it wouldn't be too hard to convert all the call sites in the backend and provide a wrapper for other users. greg On 23 Oct 2008, at 08:59 PM, Kris Jurka <books@ejurka.com> wrote: > > > 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 > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: