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:25:17
Message-ID: E1P0fnh-0000ll-3J@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
------
REL9_0_STABLE

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

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 Bruce Momjian 2010-09-28 19:42:59 pgsql: Properly close files after read file failure to prevent potentia
Previous Message Tom Lane 2010-09-28 18:51:20 pgsql: Fix another small oversight in command_no_begin patch.