Bug #531: libpq: Operations following PQfinish() work. - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #531: libpq: Operations following PQfinish() work.
Date
Msg-id 200112061835.fB6IZnx78865@postgresql.org
Whole thread Raw
Responses Re: Bug #531: libpq: Operations following PQfinish() work.  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-bugs
Anthony Chavez (anthony@xmission.com) reports a bug with a severity of 4
The lower the number the more severe it is.

Short Description
libpq: Operations following PQfinish() work.

Long Description
The PGconn *conn argument to PQfinish() is not set to NULL.  As a result, calling libpq functions---in particular,
PQexec()---afterPQfinish() has been called, continue to work until the following segmentation fault occurs: 

Program received signal SIGSEGV, Segmentation fault.
0x4044dec7 in resetPQExpBuffer () from /usr/lib/libpq.so.2

This can be misleading, and it may be wise to set conn = NULL before PQfinish() returns.

Environment: PostgreSQL 7.1.3 / RedHat Linux 7.1.


Sample Code


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: index error
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #532: backend crashes due to segmentation fault