| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: _FORTIFY_SOURCE by default? |
| Date: | 2012-09-16 18:34:56 |
| Message-ID: | 1347820496.559.6.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 2012-09-16 at 10:36 -0400, Andrew Dunstan wrote:
> Might be worth having a buildfarm animal or two building with it, say by
> setting CFLAGS before configure?
I don't really see the value in that. Either this is part of our
standard set of warnings and checks that we are interested in, and then
everyone should see it, or we don't care about this, and then we should
ignore the issue altogether. Creating different diagnostics sets for
different people and different circumstances without clear purpose one
way or the other just creates friction.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-09-16 18:54:17 | pgsql: Fix bufmgr so CHECKPOINT_END_OF_RECOVERY behaves as a shutdown c |
| Previous Message | Peter Eisentraut | 2012-09-16 18:30:57 | Re: _FORTIFY_SOURCE by default? |