| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | kuzmin(dot)db4(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19438: segfault with temp_file_limit inside cursor |
| Date: | 2026-03-30 16:29:20 |
| Message-ID: | 2333427.1774888160@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I wrote:
> Works for me. I'm done for the day but will make it so tomorrow.
Pushed that, though in the event I wrote a rather longer apologia
for why we use ERROR in one complaint and WARNING in the other.
Getting back to the original bug ... I went through tuplestore.c
and found two other places where foreseeable failures in subroutines
could leave the tuplestore in an inconsistent state. I think we
need to fix them all, per the attached draft against HEAD. The
back branches might have more/different bugs, didn't look yet.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| v2-fix-tuplestore-inconsistency-after-error.patch | text/x-diff | 1.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-03-30 18:44:18 | Re: BUG #19444: conkey field empty for domain NOT NULL constraint in pg_constraint (18.3) |
| Previous Message | Junwang Zhao | 2026-03-30 15:00:08 | Re: BUG #19446: Domain DEFAULT not reflected in system catalogs and information_schema (PG 18.3) |