From: | Matt Roberts <matt(at)runtime-collective(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | default select ordering |
Date: | 2004-10-01 15:41:52 |
Message-ID: | Pine.LNX.4.58.0410011640460.7325@molly.runtime-collective.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Please accept my apologies if this is answered elsewhere in the archives
or docs but I have searched without luck.
I've always assumed that default ordering of selects are based on a first
in first out principle and that this remains true at the row level despite
edits to columns.
However I'm dealing with a case where this doesn't seem to hold true. The
ordering has changed over time. Its difficult for me to gauge whether the
data has been moved around with pg_dump or whether optimisation/vacuum
commands have been called but I'm wondering if either of these things
could effect the first in first out ordering and if there's any system
tables or configerations that I can use to either verify or prevent this.
Any help greaty appreciated.
Matt Roberts
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Frankel | 2004-10-01 15:53:24 | Re: newby question |
Previous Message | Aleksey Serba | 2004-10-01 14:55:37 | VACUUM FULL on 24/7 server |