| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Cyril Champier <cyril(dot)champier(at)doctolib(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Default ordering option |
| Date: | 2019-07-24 20:36:36 |
| Message-ID: | 98233546-f5a4-1786-4641-1d7be8d88bc2@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2019-07-23 17:43, Cyril Champier wrote:
> In this documentation
> <https://www.postgresql.org/docs/9.1/queries-order.html>, it is said:
>
> If sorting is not chosen, the rows will be returned in an
> unspecified order. The actual order in that case will depend on the
> scan and join plan types and the order on disk, but it must not be
> relied on.
>
>
> I would like to know if there is any way to change that to have a "real"
> random behaviour.
It might be an interesting exercise to implement this as a post-parsing
hook.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Souvik Bhattacherjee | 2019-07-24 20:42:19 | Re: Running concurrent txns and measuring the timings in Postgres |
| Previous Message | Adrian Klaver | 2019-07-24 20:12:29 | Re: Running concurrent txns and measuring the timings in Postgres |