Quoting Kris Jurka <[EMAIL PROTECTED]>:
> On Wed, 4 May 2005, Mischa Sandberg wrote:
>
> > Copy makes better use of the TCP connection for transmission. COPY
> uses
> > the TCP connection like a one-way pipe. INSERT is like an RPC: the
> > sender has to wait until the insert's return statu
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> So what's the difference between a COPY and a batch of INSERT
>> statements. Also, surely, fsyncs only occur at the end of a
>> transaction, no need to fsync before a commit has been issued, right?
> With COPY, the data being inserted itself
So what's the difference between a COPY and a batch of INSERT
statements. Also, surely, fsyncs only occur at the end of a
transaction, no need to fsync before a commit has been issued, right?
With COPY, the data being inserted itself does not have to pass through
the postgresql parser.
Chris
---
On Wed, 4 May 2005, Mischa Sandberg wrote:
> Copy makes better use of the TCP connection for transmission. COPY uses
> the TCP connection like a one-way pipe. INSERT is like an RPC: the
> sender has to wait until the insert's return status roundtrips.
Not true. A client may send any number of
On 5/4/05, Mischa Sandberg <[EMAIL PROTECTED]> wrote:
> Quoting David Roussel <[EMAIL PROTECTED]>:
>
> > > COPY invokes all the same logic as INSERT on the server side
> > > (rowexclusive locking, transaction log, updating indexes, rules).
> > > The difference is that all the rows are inserted as
David Roussel wrote:
COPY invokes all the same logic as INSERT on the server side
(rowexclusive locking, transaction log, updating indexes, rules).
The difference is that all the rows are inserted as a single
transaction. This reduces the number of fsync's on the xlog,
which may be a limiting facto
Quoting David Roussel <[EMAIL PROTECTED]>:
> > COPY invokes all the same logic as INSERT on the server side
> > (rowexclusive locking, transaction log, updating indexes, rules).
> > The difference is that all the rows are inserted as a single
> > transaction. This reduces the number of fsync's on
> COPY invokes all the same logic as INSERT on the server side
> (rowexclusive locking, transaction log, updating indexes, rules).
> The difference is that all the rows are inserted as a single
> transaction. This reduces the number of fsync's on the xlog,
> which may be a limiting factor for you.
Hello,
I have a table collecting stats that shows 5 Index Tuples Fetched but no Index
Scans. Should there not be at least one Index Scan showing in the stats?
Mike
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PR
On 5/3/05, Tom Lane <[EMAIL PROTECTED]> wrote:
> Steven Rosenstein <[EMAIL PROTECTED]> writes:
> > My question is, are there any advantages, drawbacks, or outright
> > restrictions to using multiple simultaneous COPY commands to load data into
> > the same table?
>
> It will work; not sure about w
10 matches
Mail list logo