| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Emiel Hermsen <s32191234(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Case in Order By Ignored without warning or error |
| Date: | 2016-06-09 18:49:45 |
| Message-ID: | CA+bJJbzNjV59dCoi2BE1JiG3k0rnChPLkqU+5Dr-+HZ58A7t7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
David:
On Thu, Jun 9, 2016 at 5:15 PM, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> I think its a fair characterization to call "sorting on a constant" as
> "doing nothing" or "not useful". There is no noticeable difference between
> that and omitting the constant.
Yes, but in that context I wanted to point it was correctly parsing
and evaluating the expression and comparing the result ( the optimizer
may have zapped it, but this is transparent to the user ).
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AP | 2016-06-10 11:06:33 | Re: BUG #14178: output of jsonb_object and json_object doesn't match textually |
| Previous Message | hubert depesz lubaczewski | 2016-06-09 15:46:10 | PostgreSQL (9.3 and 9.6) eats all memory when using many tables |