| From: | Jeremy Schneider <schnjere(at)amazon(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: relation OID in ReorderBufferToastReplace error message |
| Date: | 2021-09-23 18:19:39 |
| Message-ID: | 04dfb298-0aa7-6cc6-968c-cac1d5fffa33@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/22/21 20:11, Amit Kapila wrote:
>
> On Thu, Sep 23, 2021 at 3:06 AM Jeremy Schneider <schnjere(at)amazon(dot)com> wrote:
>>
>> Any chance of back-patching this?
>
> Normally, we don't back-patch code improvements unless they fix some
> bug or avoid future back-patch efforts. So, I am not inclined to
> back-patch this but if others also feel strongly about this then we
> can consider it.
The original thread about the logical replication bugs spawned a few
different threads and code changes. The other code changes coming out of
those threads were all back-patched, but I guess I can see arguments
both ways on this one.
https://www.postgresql.org/message-id/flat/E1i74JE-00024V-9J%40gemulon.postgresql.org
--
Jeremy Schneider
Database Engineer
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-09-23 18:25:13 | Re: relation OID in ReorderBufferToastReplace error message |
| Previous Message | Matthias van de Meent | 2021-09-23 18:18:41 | Re: CLUSTER on partitioned index |