Re: CODE ANALYSIS FOR (an apparent error in answer from "##" (closest proximity)operator)

Поиск
Список
Период
Сортировка
От Thomas G. Lockhart
Тема Re: CODE ANALYSIS FOR (an apparent error in answer from "##" (closest proximity)operator)
Дата
Msg-id 354926E8.E8B85032@alumni.caltech.edu
обсуждение исходный текст
Ответ на [Fwd: [QUESTIONS] an apparent error in answer from "##" (closest proximity)operator]  (Gautam H Thaker <gthaker@atl.lmco.com>)
Список pgsql-hackers
> OK, I will try to work on this and provide you tested code.
> (Since this is my first attempt to code in Postgres
> it might take me a while though I have hacked for many
> years overall.)

No problem.

> Lines are more useful to me than lsegs. Is it easy
> enough to add these input/output routines so that I can
> continue to move forward prior to V6.4?

Yes. I'm starting to do that now, and we can coordinate patches. We may
as well copy the hackers list on at least our planning e-mails...

                      - Tom

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] Re: retrieving varchar size
Следующее
От: "Thomas G. Lockhart"
Дата:
Сообщение: Re: [INTERFACES] Re: [HACKERS] Revised proposal for libpq and FE/BE protocol changes