Simon Riggs wrote:
On Tue, 2008-02-05 at 15:05 +0000, Richard Huxton wrote:
Only by locking the table, which serializes access, which then slows you
down or at least restricts other options. Plus if you use pg_loader then
you'll find only the first few rows optimized and all the rest not.
Hmm - the table-locking requirement is true enough, but why would
pg_loader cause problems after the first few rows?
It runs a stream of COPY statements, so only first would be optimized
with the "empty table optimization".
Ah, if you're allowing multiple commands during the process I can see
how it could get fiddly.
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
