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:15
Message-ID: E1YCreB-0007KG-0C@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
------
REL9_2_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/821386ab7ef6dc0c711475ce19c1a0addd07c3b4

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 Noah Misch 2015-01-18 19:12:08 pgsql: Activate low-volume optional logging during regression test runs
Previous Message Andres Freund 2015-01-18 15:20:11 pgsql: Fix use of already freed memory when dumping a database's securi