The following bug has been logged online:

Bug reference: 1092
Logged by: Fred Eisele

Email address: fred (AT) netarx (DOT) com

PostgreSQL version: 7.4

Operating system: Debian/GNU unstable (kernel 2.6.3)

Description: Memory Fault in PQsetdbLogin

Details:

When opening two connections using PQsetdbLogin one of the connections was
apparently being dropped, and I would get segmentation errors.
I rebuilt the program using dmalloc and it reported...
debug-malloc library: dumping program, fatal error
Error: invalid allocation size (err 40)
....when PQsetdbLogin was called.
I replaced the call to PQsetdbLogin with an equivalent call to PQconnectdb.
dmalloc does not report any errors with PQconnectdb and the original two
problems seem to have gone away.
As far as I am concerned, deprecating PQsetdbLogin is an adequate fix.



---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

"PostgreSQL Bugs List" <pgsql-bugs (AT) postgresql (DOT) org> writes:
This is a bit hard to believe, seeing that as of 7.4 these two functions
are trivial wrappers around the same set of underlying functions.
You're going to need to provide more detail, or preferably a
reproducible test case.

regards, tom lane

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