| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: C99 compliance for src/port/snprintf.c |
| Date: | 2018-08-15 17:05:39 |
| Message-ID: | 13169.1534352739@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2018-Aug-15, Robert Haas wrote:
>> Back-patching seems a bit aggressive to me considering that the danger
>> is hypothetical.
> That was my first thought too, and my preferred path would be to make
> this master-only and only consider a backpatch later if we find some
> practical reason to do so.
Meh --- the hazards of back-patching seem to me to be more hypothetical
than the benefits. Still, I seem to be in the minority, so I withdraw
the proposal to back-patch.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-08-15 17:17:44 | Re: libpq should append auth failures, not overwrite |
| Previous Message | Tom Lane | 2018-08-15 16:46:26 | Re: libpq should append auth failures, not overwrite |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2018-08-15 18:03:16 | Re: C99 compliance for src/port/snprintf.c |
| Previous Message | Tom Lane | 2018-08-15 16:17:18 | Re: C99 compliance for src/port/snprintf.c |