Re: COPY FROM STDIN instead of INSERT

From: "Ilja Golshtein" <ilejn(at)yandex(dot)ru>
To: casey(at)pandora(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: COPY FROM STDIN instead of INSERT
Date: 2006-10-18 18:45:53
Message-ID: 45367661.000001.26259@camay.yandex.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>> Is it Ok to use COPY BINARY FROM STDIN instead of multiple INSERTs?

>I don't think I would use BINARY, it seems likely to be susceptible
>to changes in the underlying data type storage. From the docs:
>"To determine the appropriate binary format for the actual tuple data
>you should consult the PostgreSQL source

[skipped]

Yes, it's a problem, though it's solved already. I use BINARY for, say, initial data loading.

>AFIAK, the locking semantics are the same as INSERT, i.e., it
>does not lock the entire table or anything like that. Since it would
>allow transactions that insert data to finish faster, it should
>actually work better under high concurrency.

Do hope that's right.

Thanks.

--
Best regards
Ilja Golshtein

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Karen Hill 2006-10-18 18:50:32 Re: division by zero error in a request
Previous Message Tom Lane 2006-10-18 18:31:27 Re: Stats Collector Won't Start