| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Huansong Fu <huansong(dot)fu(dot)info(at)gmail(dot)com> |
| Cc: | Quan Zongliang <quanzongliang(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: bugfix: invalid bit/varbit input causes the log file to be unreadable |
| Date: | 2021-12-13 20:33:30 |
| Message-ID: | 870931.1639427610@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Huansong Fu <huansong(dot)fu(dot)info(at)gmail(dot)com> writes:
> We recently saw a similar issue in v12 and wondered why the corresponding fix for v14 (https://github.com/postgres/postgres/commit/16e3ad5d143) was not backported to v13 and before. The commit message did mention that this fix might have problem with translatable string messages - would you mind providing a bit more context about what is needed to backport this fix? Thank you.
Well, the commit message lists the reasons for not back-patching:
* we've seen few field complaints about such problems
* it'd add work for translators
* it wouldn't work reliably before v12.
Perhaps there's a case for back-patching as far as v12,
but I can't get very excited about it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-12-13 20:36:24 | Re: O(n) tasks cause lengthy startups and checkpoints |
| Previous Message | Andres Freund | 2021-12-13 20:01:51 | Re: isolationtester: add session name to application name |