Re: Allowing printf("%m") only where it actually works
От
Nico Williams
Тема
Re: Allowing printf("%m") only where it actually works
Дата
Msg-id
20180819182704.GC16780@localhost
Ответ на
Список
Дерево обсуждения
Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Thomas Munro <thomas.munro@enterprisedb.com>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Thomas Munro <thomas.munro@enterprisedb.com>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Thomas Munro <thomas.munro@enterprisedb.com>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Thomas Munro <thomas.munro@enterprisedb.com>
Re: Allowing printf("%m") only where it actually works Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Nico Williams <nico@cryptonector.com>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Nico Williams <nico@cryptonector.com>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Michael Paquier <michael@paquier.xyz>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Michael Paquier <michael@paquier.xyz>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Michael Paquier <michael@paquier.xyz>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Michael Paquier <michael@paquier.xyz>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Andres Freund <andres@anarazel.de>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Andres Freund <andres@anarazel.de>
Re: Allowing printf("%m") only where it actually works Andres Freund <andres@anarazel.de>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Andres Freund <andres@anarazel.de>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Andres Freund <andres@anarazel.de>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Andres Freund <andres@anarazel.de>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Robert Haas <robertmhaas@gmail.com>
Re: Allowing printf("%m") only where it actually works Fabien COELHO <coelho@cri.ensmp.fr>
Re: Allowing printf("%m") only where it actually works Tom Lane <tgl@sss.pgh.pa.us>
Re: Allowing printf("%m") only where it actually works Fabien COELHO <coelho@cri.ensmp.fr>
Re: Allowing printf("%m") only where it actually works Thomas Munro <thomas.munro@enterprisedb.com>
On Sun, Aug 19, 2018 at 01:15:58AM -0400, Tom Lane wrote: > Nico Williams writes: > > On Sat, Aug 18, 2018 at 04:34:50PM -0400, Tom Lane wrote: > >> So now I'm about ready to propose that we just *always* use > >> snprintf.c, and forget all of the related configure probing. > > > You'd also get to ensure that all uses from *die() are > > async-signal-safe. > > [ raised eyebrow... ] That seems like more than I care to promise > here. But even if snprintf itself were unconditionally safe, > there's plenty of other stuff in that code path that isn't. One step at a time, no? And there's the other benefits.
В списке pgsql-hackers по дате отправления
От: Jonathan S. Katz
Дата: