Queries which returned tuples with many consecutive null fields would confuse the libpq protocol.
Thanks to Adam Richter (adam@yggdrasil.com) for finding the fixing the bug.
Apply this patch.
======================================================================
diff -c -r1.3 RELEASE.patchlevel
*** 1.3 1995/10/31 07:43:29
--- RELEASE.patchlevel 1995/10/31 07:43:51
***************
*** 3,10 ****
## This file is used to maintain sequencing of patches
version: 1.0
! patch level: 12
! patch date: Mon Oct 30 23:22:44 PST 1995
--- 3,10 ----
## This file is used to maintain sequencing of patches
version: 1.0
! patch level: 13
! patch date: Mon Oct 30 23:42:24 PST 1995
===================================================================
*** 1.8 1995/08/12 20:05:51
--- src/libpq/fe-exec.c 1995/10/31 06:49:22
***************
*** 130,137 ****
nbytes = nfields / BYTELEN;
if ( (nfields % BYTELEN) > 0)
nbytes++;
!
! if (pqGets(bitmap, nbytes, Pfin, Pfdebug) == 1){
sprintf(conn->errorMessage,
"Error reading null-values bitmap from tuple data stream\n");
return NULL;
--- 130,137 ----
nbytes = nfields / BYTELEN;
if ( (nfields % BYTELEN) > 0)
nbytes++;
!
! if (pqGetnchar(bitmap, nbytes, Pfin, Pfdebug) == 1){
sprintf(conn->errorMessage,
"Error reading null-values bitmap from tuple data stream\n");
return NULL;