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)

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match