| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dmitri Koulikov <koulikoff(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #12137: ORDER BY with expresion changes the output if added |
| Date: | 2014-12-09 18:00:13 |
| Message-ID: | 6262.1418148013@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Dmitri Koulikov <koulikoff(at)gmail(dot)com> writes:
> Hello. I've prepared a sample. It turned out that the problem lies in other
> place.
> In the attachment there is output from explain and a sample
This isn't a self-contained test case :-(. I guessed at some index
definitions but couldn't reproduce the plan exactly, and in any case
it's clear from your EXPLAIN output there are more than just these
three rows in your tables.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-12-09 18:24:54 | Re: regression, deadlock in high frequency single-row UPDATE |
| Previous Message | Andres Freund | 2014-12-09 17:43:20 | Re: regression, deadlock in high frequency single-row UPDATE |