Re: Using multi-row technique with COPY - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Using multi-row technique with COPY
Date
Msg-id 7158.1133276647@sss.pgh.pa.us
Whole thread Raw
In response to Re: Using multi-row technique with COPY  (Harald Fuchs <hf0923x@protecting.net>)
List pgsql-hackers
Harald Fuchs <hf0923x@protecting.net> writes:
> In article <20051129004435.GR78939@pervasive.com>,
> "Jim C. Nasby" <jnasby@pervasive.com> writes:
>> Does that mean that this fast copy would end up not re-using space on
>> pages that have space available? ISTM that's something users would want
>> to be able to over-ride. In fact, it seems like it shouldn't be a
>> default behavior...

> Why not?  If you later do INSERT/UPDATE/DELETE, space will get reused
> anyway, and if you don't (i.e. one-time bulk load on a constant
> table), you should afterwards do a VACUUM FULL ANALYZE anyway.

You lost me at the "FULL" part.

In general, any "optimization" proposal that requires VACUUM FULL as
part of normal operation is a lost cause.  You should instead be
thinking about procedures that won't require a VACUUM FULL, ever.
        regards, tom lane


pgsql-hackers by date:

Previous
From: David Boreham
Date:
Subject: Re: ice-broker scan thread
Next
From: Martijn van Oosterhout
Date:
Subject: Re: ice-broker scan thread