| From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
| Cc: | Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Alter Table Command Rearranges Rows |
| Date: | 2010-09-17 20:39:44 |
| Message-ID: | AANLkTimeY-C1RD+socRqRFe2uubRRODhL9eMa5pyZgsH@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Sep 17, 2010 at 1:32 PM, Michael Glaesemann
<grzm(at)seespotcode(dot)net> wrote:
> Postgres (nor any other SQL RDBMS) does not guarantee row order unless you specify it with an ORDER BY clause.
This is true, but some database will maintain a tables clustering.
MS-Access comes to mind. I don't know if MySQL does this also.
In PostgreSQL you can issue a periodic cluster command on the primary
key. But as mentioned it is a bad practice to rely on the physical
ordering of the table.
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bricklen | 2010-09-17 20:58:09 | Re: How to generate XML output from a Store Procedure |
| Previous Message | Joshua J. Kugler | 2010-09-17 20:39:23 | Re: missing chunk number 497 for toast value 504723663 |