From: | Jan Schulz <jasc(at)gmx(dot)net> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Fwd: BUG #14948: cost overflow |
Date: | 2017-12-05 17:50:38 |
Message-ID: | CAAc324irfhEszHHWcomc6HC5_+6+N3Ryvc=WUqzLVW7ALvj7VQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
[resent to the list, sorry Alvaro]
Hello,
On 5 December 2017 at 13:39, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> it seems pretty likely that these are indeed overflows. However,
> because of the whitespace mangling these plans are pretty much
> impossible to read. Would you mind pasting these again, as text/plain
> attachment instead?
I attached the plans in plain text.
> Does the query actually take 6ms in the system with the funny explain,
> and 5s on the other?
I didn't really noticed the timings, could be. I was more surprised
that the broken plan actually resulted in zero rows because it should
have had some.
Kind regards,
Jan
--
Jan Schulz
mail: jasc(at)gmx(dot)net
Attachment | Content-Type | Size |
---|---|---|
broken_plan.txt | text/plain | 41.8 KB |
good_plan.txt | text/plain | 37.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Todd A. Cook | 2017-12-05 21:23:02 | Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop |
Previous Message | Jan Schulz | 2017-12-05 17:48:42 | Re: BUG #14948: cost overflow |