From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@postgreSQL.org
Subject: Obsolete coding in fork_process.c
Date: Thu, 01 May 2014 12:13:28 -0400
Message-ID: <30040.1398960808@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

fork_process.c quoth:

    /*
     * Flush stdio channels just before fork, to avoid double-output problems.
     * Ideally we'd use fflush(NULL) here, but there are still a few non-ANSI
     * stdio libraries out there (like SunOS 4.1.x) that coredump if we do.
     * Presently stdout and stderr are the only stdio output channels used by
     * the postmaster, so fflush'ing them should be sufficient.
     */
    fflush(stdout);
    fflush(stderr);

Is there any reason not to change this to just fflush(NULL)?  We dropped
support for SunOS 4.1 quite some time ago ...

While it's still true that the postmaster proper doesn't need to fflush
anything but stdout and stderr, this coding seems a bit less than safe
when you consider the possibility of third-party libraries loaded into the
postmaster process.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers