Re: dump/restore doesn't preserve row ordering? - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: dump/restore doesn't preserve row ordering?
Date
Msg-id CACjxUsOXK+iNW5Rj44u64WoRoWWPArADvLRi4CxytTZaS+ed+g@mail.gmail.com
Whole thread Raw
In response to Re: dump/restore doesn't preserve row ordering?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Aug 23, 2016 at 8:43 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> It's interesting that nobody has complained about this behavior.

We have been known to emphasize that unless you have an ORDER BY
clause at the outermost level of a query, there is no guarantee
about the order of rows returned.  In general, even with autovacuum
off and no DML running, the same query can return rows in a
different order because of synchronized scans -- so I would tend to
view the lack of complaints as a sign of the maturity and awareness
of the user base.

Of course, it can still be an inconvenience for testing, but that's
a different issue.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: Strange result with LATERAL query
Next
From: Tom Lane
Date:
Subject: Re: Showing parallel status in \df+