The following bug has been logged online:

Bug reference: 1897
Logged by: Wade Hampton
Email address: wade.hampton (AT) nsc1 (DOT) net
PostgreSQL version: 8.0.3-1
Operating system: Fedora Core 4
Description: dmalloc memory error on PQconnectdb
Details:

I have a multithreaded application using Postgresql and am testing for
memory leaks. I compiled and linked with dmallocth. My PGconnect() is now
causing a dmalloc abort. The error appears to be a calloc of 0 elements of
40 bytes in libkrb5, called from libpq.

The connection is to: hostaddr = 127.0.0.1 dbname = mydb

The same code with dmalloc works fine with Fedora Core 2.0, Postgresql
7.4.7-3.

There was a report of a similar problem in earlier versions:

http://www.mail-archive.com/pgsql-bu.../msg08081.html

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

"Wade Hampton" <wade.hampton (AT) nsc1 (DOT) net> writes:
(1) Why is that a bug? calloc of 0 elements is explicitly allowed by
the Single Unix Spec:
http://www.opengroup.org/onlinepubs/...sh/calloc.html

(2) If you do think it's a bug, why are you complaining to us rather
than to the Kerberos people?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match