pgsql: Properly close files after read file failure to prevent potentia

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Properly close files after read file failure to prevent potentia
Date: 2010-09-28 19:42:59
Message-ID: E1P0g4p-0000zZ-FJ@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Properly close files after read file failure to prevent potential
resource leak. Of course, any such failure aborts pg_upgrade, but might
as well be clean about it.

Per patch from Grzegorz Ja?kiewicz.

Branch
------
master

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f175884520949fbc52908d2f4b2baacde5906ebc

Modified Files
--------------
contrib/pg_upgrade/file.c | 3 +++
contrib/pg_upgrade/page.c | 3 +++
2 files changed, 6 insertions(+), 0 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-09-28 20:15:39 pgsql: Fix incorrect usage of non-strict OR joinclauses in appendrel in
Previous Message Bruce Momjian 2010-09-28 19:25:17 pgsql: Properly close files after read file failure to prevent potentia