| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Duncan Sands <duncan(dot)sands(at)deepbluecap(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Subject: | Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 |
| Date: | 2025-06-23 14:05:35 |
| Message-ID: | CAD21AoAf6-j0vPTpzUj-Q2ySPo-jW11+-pN3kmeSBypgwUZaSg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jun 23, 2025 at 9:03 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
> Dear Sawada-san,
>
> > One solution is to have two expected-output files to cover both cases.
> > We do a similar thing for the plpgsql_cache.sql test case. What do you
> > think?
>
> Personally I don't like the approach because XXX_1.out can be easily missed to be
> updated, but it is not a strong opinion.
I think that we have only a few releases for v13 and there would not
likely be many cases where we need to update _1.out file. But I'm open
to other ideas. Do you prefer removing the test from v13? I'm not sure
that just because it's easy to miss updating a _1.out file is a good
reason to remove tests.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-06-23 18:24:01 | Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references |
| Previous Message | Hayato Kuroda (Fujitsu) | 2025-06-23 12:03:33 | RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 |