pgsql: Fix use of already freed memory when dumping a database's securi

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix use of already freed memory when dumping a database's securi
Date: 2015-01-18 15:20:05
Message-ID: E1YCre1-0007JC-EU@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix use of already freed memory when dumping a database's security label.

pg_dump.c:dumDatabase() called ArchiveEntry() with the results of a a
query that was PQclear()ed a couple lines earlier.

Backpatch to 9.2 where security labels for shared objects where
introduced.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/525b84c576e119de7f2b0d00e3a99d559771aa7b

Modified Files
--------------
src/bin/pg_dump/pg_dump.c | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2015-01-18 15:20:08 pgsql: Fix use of already freed memory when dumping a database's securi
Previous Message Peter Eisentraut 2015-01-18 03:43:14 pgsql: Fix namespace handling in xpath function