Re: CODE ANALYSIS FOR (an apparent error in answer from "##" (closest proximity)operator) - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: CODE ANALYSIS FOR (an apparent error in answer from "##" (closest proximity)operator)
Date
Msg-id 354926E8.E8B85032@alumni.caltech.edu
Whole thread Raw
In response to [Fwd: [QUESTIONS] an apparent error in answer from "##" (closest proximity)operator]  (Gautam H Thaker <gthaker@atl.lmco.com>)
List 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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: retrieving varchar size
Next
From: "Thomas G. Lockhart"
Date:
Subject: Re: [INTERFACES] Re: [HACKERS] Revised proposal for libpq and FE/BE protocol changes