| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: backtrace_on_internal_error |
| Date: | 2023-12-08 13:21:32 |
| Message-ID: | da4a680a-5d8a-4663-a5c8-a3ccbf23394a@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Here is a patch to play with.
I also found a related typo.
One possible question for discussion is whether the default for this
should be off, on, or possibly something like on-in-assert-builds.
(Personally, I'm happy to turn it on myself at run time, but everyone
has different workflows.)
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Fix-variable-name-and-comment.patch | text/plain | 1.6 KB |
| v1-0002-Add-GUC-backtrace_on_internal_error.patch | text/plain | 4.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2023-12-08 13:27:54 | Re: Assert failure on 'list_member_ptr(rel->joininfo, restrictinfo)' |
| Previous Message | Nikolay Shaplov | 2023-12-08 13:04:05 | Re: [PATCH] New [relation] option engine |