| From: | Jim Nasby <decibel(at)decibel(dot)org> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| Cc: | Jack Orenstein <jorenstein(at)archivas(dot)com>, gustavo halperin <ggh(dot)develop(at)gmail(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: postgresql vs mysql |
| Date: | 2007-02-22 23:17:35 |
| Message-ID: | 8F7BDC6B-AA29-40AC-A594-911DA3BDA5A7@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Feb 21, 2007, at 10:26 AM, Scott Marlowe wrote:
> The only thing I can think of that rewrites a whole postgresql table
> would be reindexing it, or an update without a where clause (or a
> where
> clause that includes every row). Normal operations, like create
> index,
> add column, drop column, etc do not need to rewrite the table and
> happen
> almost instantly.
Reindexing won't re-write a table; clustering will. Also some ALTER
TABLE commands will (such as changing the data type of a column, or
creating a new column that's NOT NULL).
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Walker | 2007-02-22 23:20:55 | Re: php professional |
| Previous Message | Jim Nasby | 2007-02-22 23:14:11 | Re: postgresql vs mysql |