pgsql: Restore psql's SIGPIPE setting if popen() fails.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Restore psql's SIGPIPE setting if popen() fails.
Date: 2016-12-07 17:39:46
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Restore psql's SIGPIPE setting if popen() fails.

Ancient oversight in PageOutput(): if popen() fails, we'd better reset
the SIGPIPE handler before returning stdout, because ClosePager() won't.
Noticed while fixing the empty-PAGER issue.

Branch
------
REL9_5_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/93c78ba19b378b4b54dad5ceb4fdf063bb0998e1

Modified Files
--------------
src/bin/psql/print.c | 2 ++
1 file changed, 2 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-12-07 18:20:01 pgsql: Implement table partitioning.
Previous Message Tom Lane 2016-12-07 17:20:17 pgsql: Handle empty or all-blank PAGER setting more sanely in psql.