| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Erik Brandsberg <erik(at)heimdalldata(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martin Handsteiner <martin(dot)handsteiner(at)sibvisions(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: AW: Optimizer Hint, to ignore limit and offset in optimizer plan |
| Date: | 2020-06-29 15:48:01 |
| Message-ID: | 20200629154801.GA17530@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Mon, Jun 29, 2020 at 10:33:43AM -0400, Erik Brandsberg wrote:
> New request: If order by is not specified with an order by clause, allow an
> option to be set that explicitly randomizes the results to break everything
> that relies on the order. :) This would primarily be used for QA work to find
> code that depends on an undefined order.
You mean LIMIT/OFFSET without ORDER BY? I think issuing a warning,
perhaps when some "novice" mode is enabled, would work well.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Handsteiner | 2020-06-29 17:33:10 | AW: AW: Optimizer Hint, to ignore limit and offset in optimizer plan |
| Previous Message | Erik Brandsberg | 2020-06-29 14:33:43 | Re: AW: Optimizer Hint, to ignore limit and offset in optimizer plan |