Re: VACUUM FULL changes the order of rows in a table? - Mailing list pgsql-bugs

From Tom Lane
Subject Re: VACUUM FULL changes the order of rows in a table?
Date
Msg-id 9569.1027496565@sss.pgh.pa.us
Whole thread Raw
In response to VACUUM FULL changes the order of rows in a table?  (Douglas Trainor <trainor@uic.edu>)
List pgsql-bugs
Douglas Trainor <trainor@uic.edu> writes:
> WARNING:  Not sure if what I am about to describe is a bug.

As Scott comments, it isn't.  Under *no* circumstances does Postgres
guarantee anything about the physical order of rows in a table.
This is entirely in accordance with the SQL spec --- row ordering is
not considered significant at all in the computational model.  It's
worth noting that ORDER BY is treated by the spec as a mere output
decoration issue; you cannot ORDER the result of a sub-select, only
the final results being sent to the client.  Fundamentally SQL does
not think row order is a valid consideration at all.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_ctl -w option does not behave as documented
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #718: request for improvement of /? to show /d+ /l+ commands