| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Kevin Murphy <murphy(at)genome(dot)chop(dot)edu> |
| Cc: | PostgreSQL general <pgsql-general(at)postgresql(dot)org>, Neil Conway <neilc(at)samurai(dot)com> |
| Subject: | Re: CLUSTER equivalent |
| Date: | 2005-09-15 21:35:05 |
| Message-ID: | 20050915213505.GD29323@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Sep 15, 2005 at 05:09:51PM -0400, Kevin Murphy wrote:
> Neil Conway wrote:
>
> >Kevin Murphy wrote:
> >
> >>I just wanted to confirm that the COPY command always stores data in
> >>the table in the order in which it appears in the import file.
> >
> >This is not the case -- depending on the content of the FSM, the newly
> >added rows might be distributed throughout the table.
>
> How about for a freshly created, empty table -- I should have qualified
> my original statement.
In that particular case, the answer is yes. As is if you TRUNCATE the
table just prior to the COPY.
--
Alvaro Herrera -- Valdivia, Chile Architect, www.EnterpriseDB.com
"El destino baraja y nosotros jugamos" (A. Schopenhauer)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Fitzpatrick | 2005-09-15 22:48:59 | Create a pg table from CSV with header rows |
| Previous Message | Kevin Murphy | 2005-09-15 21:09:51 | Re: CLUSTER equivalent |