Date: Mon, 29 Jun 2020 11:48:01 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Erik Brandsberg <erik@heimdalldata.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
	Martin Handsteiner <martin.handsteiner@sibvisions.com>,
	Simon Riggs <simon@2ndquadrant.com>,
	"pgsql-sql@lists.postgresql.org" <pgsql-sql@lists.postgresql.org>
Subject: Re: AW: Optimizer Hint, to ignore limit and offset in optimizer plan
Message-ID: <20200629154801.GA17530@momjian.us>
References: 
 <VI1PR1001MB1423F5361320BB854708FD2FE8930@VI1PR1001MB1423.EURPRD10.PROD.OUTLOOK.COM>
 <CANP8+jLYmta=WfEpbP-DihtNkD7VKhbEzMyOkYUjuBCvWEZfdw@mail.gmail.com>
 <VI1PR1001MB1423793F6E5624602BD2DEAFE86E0@VI1PR1001MB1423.EURPRD10.PROD.OUTLOOK.COM>
 <323666.1593441019@sss.pgh.pa.us>
 <CAFcck8H+4kWzYTc_TFzn1GF-1u39hU66RskSVbeWr12CGnzFaQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAFcck8H+4kWzYTc_TFzn1GF-1u39hU66RskSVbeWr12CGnzFaQ@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

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@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee