PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID15627
PG Version11.1
OSUbuntu 18.04.1 LTS
Opened2019-02-10 16:30:29+00
Reported byice ice
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      15627
Logged by:          ice ice
Email address:      (redacted)
PostgreSQL version: 11.1
Operating system:   Ubuntu 18.04.1 LTS
Description:        

PQisBusy has memory leak with next valgrind stack:

  1: malloc in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so
  2: PQmakeEmptyPGresult in
/opt/src/postgres/src/interfaces/libpq/fe-exec.c:146
  3: getRowDescriptions in
/opt/src/postgres/src/interfaces/libpq/fe-protocol3.c:492
  4: pqParseInput3 in
/opt/src/postgres/src/interfaces/libpq/fe-protocol3.c:293
  5: parseInput in /opt/src/postgres/src/interfaces/libpq/fe-exec.c:1747
  6: PQisBusy in /opt/src/postgres/src/interfaces/libpq/fe-exec.c:1764

The problem is that if PQisBusy doesn't revoke memory for item

/* Status for asynchronous result construction */
	PGresult   *result;			/* result being constructed */

in struct pg_conn

Messages

DateAuthorSubject
2019-02-10 16:30:29+00PG Bug reporting formBUG #15627: libpq memory leak
2019-02-10 17:03:07+00Tom LaneRe: BUG #15627: libpq memory leak
2019-02-10 21:20:32+00Sergey IvanovRe: BUG #15627: libpq memory leak