After experiencing so many problems with 7.3.2, I decided to test
7.4-snapshot. It failed only on one test, instead of 17.
NetBSD-1.6 / Alpha (64-bit)
Postgresql-7.4-snapshot-2003-03-24
The error I'm getting is:
! ERROR: datumGetSize: Invalid typLen 0
That error caused many problems in 7.3.2. I sent an email about this but
it must be stuck in the queue because it had an attachment of 234k.
---------------------------
*** ./expected/opr_sanity.out Tue Jan 28 16:13:41 2003
--- ./results/opr_sanity.out Wed Mar 26 22:08:17 2003
***************
*** 46,55 ****
p1.proname = p2.proname AND
p1.pronargs = p2.pronargs AND
p1.proargtypes = p2.proargtypes;
! oid | proname | oid | proname
! -----+---------+-----+---------
! (0 rows)
!
-- Considering only built-in procs (prolang = 12), look for multiple
uses
-- of the same internal function (ie, matching prosrc fields). It's OK
to
-- have several entries with different pronames for the same internal
function,
--- 46,52 ----
p1.proname = p2.proname AND
p1.pronargs = p2.pronargs AND
p1.proargtypes = p2.proargtypes;
! ERROR: datumGetSize: Invalid typLen 0
-- Considering only built-in procs (prolang = 12), look for multiple
uses
-- of the same internal function (ie, matching prosrc fields). It's OK
to
-- have several entries with different pronames for the same internal
function,
***************
*** 276,285 ****
p1.oprkind = p2.oprkind AND
p1.oprleft = p2.oprleft AND
p1.oprright = p2.oprright;
! oid | oprcode | oid | oprcode
! -----+---------+-----+---------
! (0 rows)
!
-- Look for commutative operators that don't commute.
-- DEFINITIONAL NOTE: If A.oprcom = B, then x A y has the same result as
y B x.
-- We expect that B will always say that B.oprcom = A as well; that's
not
--- 273,279 ----
p1.oprkind = p2.oprkind AND
p1.oprleft = p2.oprleft AND
p1.oprright = p2.oprright;
! ERROR: datumGetSize: Invalid typLen 0
-- Look for commutative operators that don't commute.
-- DEFINITIONAL NOTE: If A.oprcom = B, then x A y has the same result as
y B x.
-- We expect that B will always say that B.oprcom = A as well; that's
not
======================================================================
--
Thomas
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
