pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex 6+ messages / 1 participants [nested] [flat]
* pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex @ 2014-05-15 01:14 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-15 01:14 UTC (permalink / raw) To: pgsql-committers In initdb, ensure stdout/stderr buffering behavior is what we expect. Since this program may print to either stdout or stderr, the relative ordering of its messages depends on the buffering behavior of those files. Force stdout to be line-buffered and stderr to be unbuffered, ensuring that the behavior will match standard Unix interactive behavior, even when stdout and stderr are rerouted to a file. Per complaint from Tomas Vondra. The particular case he pointed out is new in HEAD, but issues of the same sort could arise in any branch with other error messages, so back-patch to all branches. I'm unsure whether we might not want to do this in other client programs as well. For the moment, just fix initdb. Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/2dc4f011fd61501cce507be78c39a2677690d44b Modified Files -------------- src/bin/initdb/initdb.c | 9 +++++++++ 1 file changed, 9 insertions(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex @ 2014-05-15 01:14 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-15 01:14 UTC (permalink / raw) To: pgsql-committers In initdb, ensure stdout/stderr buffering behavior is what we expect. Since this program may print to either stdout or stderr, the relative ordering of its messages depends on the buffering behavior of those files. Force stdout to be line-buffered and stderr to be unbuffered, ensuring that the behavior will match standard Unix interactive behavior, even when stdout and stderr are rerouted to a file. Per complaint from Tomas Vondra. The particular case he pointed out is new in HEAD, but issues of the same sort could arise in any branch with other error messages, so back-patch to all branches. I'm unsure whether we might not want to do this in other client programs as well. For the moment, just fix initdb. Branch ------ REL9_3_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/4511e6c831e3d16303d6df183a00d33f5d6ba3e8 Modified Files -------------- src/bin/initdb/initdb.c | 9 +++++++++ 1 file changed, 9 insertions(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex @ 2014-05-15 01:14 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-15 01:14 UTC (permalink / raw) To: pgsql-committers In initdb, ensure stdout/stderr buffering behavior is what we expect. Since this program may print to either stdout or stderr, the relative ordering of its messages depends on the buffering behavior of those files. Force stdout to be line-buffered and stderr to be unbuffered, ensuring that the behavior will match standard Unix interactive behavior, even when stdout and stderr are rerouted to a file. Per complaint from Tomas Vondra. The particular case he pointed out is new in HEAD, but issues of the same sort could arise in any branch with other error messages, so back-patch to all branches. I'm unsure whether we might not want to do this in other client programs as well. For the moment, just fix initdb. Branch ------ REL8_4_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/52d2f887d21a3649ea573b31f3a1b9dd5b68ea85 Modified Files -------------- src/bin/initdb/initdb.c | 9 +++++++++ 1 file changed, 9 insertions(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex @ 2014-05-15 01:14 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-15 01:14 UTC (permalink / raw) To: pgsql-committers In initdb, ensure stdout/stderr buffering behavior is what we expect. Since this program may print to either stdout or stderr, the relative ordering of its messages depends on the buffering behavior of those files. Force stdout to be line-buffered and stderr to be unbuffered, ensuring that the behavior will match standard Unix interactive behavior, even when stdout and stderr are rerouted to a file. Per complaint from Tomas Vondra. The particular case he pointed out is new in HEAD, but issues of the same sort could arise in any branch with other error messages, so back-patch to all branches. I'm unsure whether we might not want to do this in other client programs as well. For the moment, just fix initdb. Branch ------ REL9_1_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/360ec00a57964ce27c4ee064b7313d55dbf2fb9f Modified Files -------------- src/bin/initdb/initdb.c | 9 +++++++++ 1 file changed, 9 insertions(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex @ 2014-05-15 01:14 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-15 01:14 UTC (permalink / raw) To: pgsql-committers In initdb, ensure stdout/stderr buffering behavior is what we expect. Since this program may print to either stdout or stderr, the relative ordering of its messages depends on the buffering behavior of those files. Force stdout to be line-buffered and stderr to be unbuffered, ensuring that the behavior will match standard Unix interactive behavior, even when stdout and stderr are rerouted to a file. Per complaint from Tomas Vondra. The particular case he pointed out is new in HEAD, but issues of the same sort could arise in any branch with other error messages, so back-patch to all branches. I'm unsure whether we might not want to do this in other client programs as well. For the moment, just fix initdb. Branch ------ REL9_2_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/a2655a32226ac9f310beea7ee786c573f8009bd6 Modified Files -------------- src/bin/initdb/initdb.c | 9 +++++++++ 1 file changed, 9 insertions(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex @ 2014-05-15 01:14 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-15 01:14 UTC (permalink / raw) To: pgsql-committers In initdb, ensure stdout/stderr buffering behavior is what we expect. Since this program may print to either stdout or stderr, the relative ordering of its messages depends on the buffering behavior of those files. Force stdout to be line-buffered and stderr to be unbuffered, ensuring that the behavior will match standard Unix interactive behavior, even when stdout and stderr are rerouted to a file. Per complaint from Tomas Vondra. The particular case he pointed out is new in HEAD, but issues of the same sort could arise in any branch with other error messages, so back-patch to all branches. I'm unsure whether we might not want to do this in other client programs as well. For the moment, just fix initdb. Branch ------ REL9_0_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/5e798475cc4f23ac2a68d254a5db2e57995a870e Modified Files -------------- src/bin/initdb/initdb.c | 9 +++++++++ 1 file changed, 9 insertions(+) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2014-05-15 01:14 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2014-05-15 01:14 pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex Tom Lane <tgl@sss.pgh.pa.us> 2014-05-15 01:14 pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex Tom Lane <tgl@sss.pgh.pa.us> 2014-05-15 01:14 pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex Tom Lane <tgl@sss.pgh.pa.us> 2014-05-15 01:14 pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex Tom Lane <tgl@sss.pgh.pa.us> 2014-05-15 01:14 pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex Tom Lane <tgl@sss.pgh.pa.us> 2014-05-15 01:14 pgsql: In initdb, ensure stdout/stderr buffering behavior is what we ex Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox