| From: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
|---|---|
| To: | James Coleman <jtc331(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: enable_incremental_sort changes query behavior |
| Date: | 2020-10-03 14:54:36 |
| Message-ID: | CAJGNTeN4E+uUavUBRXRKG5GacPGh+69d-Vu582OuXsCtPLS8fQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 3 Oct 2020 at 08:15, James Coleman <jtc331(at)gmail(dot)com> wrote:
>
> Jaime: was the backtrace in the original report by any chance record
> from breakpointing in the first call to get_sortgroupref_tle() (and
> one that successfully returned a sort group ref) rather than a call
> that hit the elog error on line 379?
>
I remember the first backtrace a made for this was on the line of the
elog but then a second backtrace was with the function, now that
repeat it with line of the function for the elog (and the original
query) i see again create_incrementalsort_plan() which made me try
with enable_incremental_sort disabled...
sorry for that, attached a better backtrace
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| gdb.txt | text/plain | 13.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-10-03 14:57:34 | Re: <xref> vs <command> formatting in the docs |
| Previous Message | James Coleman | 2020-10-03 14:50:06 | Re: enable_incremental_sort changes query behavior |