| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Two remaining shmem attachment issues in single-user mode |
| Date: | 2026-09-23 05:26:30 |
| Message-ID: | 966D70CF-A6FD-48E6-9843-04B87FFF99AE@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Sep 23, 2026, at 02:52, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> wrote:
>
> On Sun, Sep 20, 2026 at 1:28 AM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>> Also, for v1-0001, I personally don't feel that the new test is really necessary. This doesn't seem like particularly fragile logic that's likely to regress accidentally,
>
> (But the claim being made is that it _did_ regress accidentally, right?)
>
>> and I've noticed that Tom generally seems reluctant to increase test runtime, even by a very small amount, unless the test provides clear value.
>
> I haven't reviewed the whole patch, but as someone who'd really prefer
> that every bug fix be accompanied by a regression test if possible, I
> don't think we should be discouraging people from writing them. Don't
> waste resources, sure, but don't avoid writing tests. A committer can
> always strip an overly-expensive test out before committing.
>
That’s a good point. Noted.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeevan Chalke | 2026-09-23 05:50:11 | Re: postgres_fdw: push down FETCH FIRST .. WITH TIES when server version allows |
| Previous Message | Chao Li | 2026-09-23 05:21:33 | Re: [PATCH] Explain what the default output_plugin_libraries do |