[Fwd: [QUESTIONS] an apparent error in answer from "##" (closest proximity)operator]

Started by Gautam H Thakerover 27 years ago2 messages
#1Gautam H Thaker
gthaker@atl.lmco.com

Hi,

sorry to bug you as an individual, but I had no replies
at all to my postings below. Can you point me to a
place/person/source where I might try to seek an answer?

Thanks.

Gautam

=======
1st posting (2nd posting attached to this email.)
========
I am trying

drop table lines;
DROP

create table lines (
l line
);
CREATE

insert into lines values ('((0,0),(1,2))'::line);
WARN:fmgr_info: function 0: cache lookup failed

EOF

If I change line to lseg everthing work ok.

I believe this is Postgres 6.3 (but I don't know how to
readily find that out on a running/installed version.
Is there a way to know by looking into some file someplace?)

Thanks

--
Gautam H. Thaker
Distributed Processing Lab; Lockheed Martin Adv. Tech. Labs
A&E 3W; 1 Federal Street; Camden, NJ 08102
609-338-3907, fax 609-338-4144 email: gthaker@atl.lmco.com

#2Thomas G. Lockhart
lockhart@alumni.caltech.edu
In reply to: Gautam H Thaker (#1)
Re: CODE ANALYSIS FOR (an apparent error in answer from "##" (closest proximity)operator)

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