Peter Geoghegan <p...@heroku.com> writes:
> On Wed, Jan 21, 2015 at 10:14 AM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> This isn't a back-patchable bug fix, but given the lack of prior
>> complaints, maybe it doesn't matter. Alternatively, we could back-patch
>> only the addition of escape_string_warning to the struct: that would fit
>> into padding space in the struct so that there would be no ABI risk.
> I think that this is a good idea, but I see very little reason to
> back-patch. I'm not aware that the "padding space" argument has been
> used for something like this before.
Oh, we definitely *have* done that kind of thing in the past, when there
was sufficient motivation. But I'm not sure there's sufficient motivation
here.
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
