Re: psql copy command - 1 char limitation on delimiter - Mailing list pgsql-general

From Merlin Moncure
Subject Re: psql copy command - 1 char limitation on delimiter
Date
Msg-id AANLkTikRwGi6kUXzVPfdFYV=j-97XUNeddrGChE1B3-=@mail.gmail.com
Whole thread Raw
In response to Re: psql copy command - 1 char limitation on delimiter  (rey <reywang@optonline.net>)
List pgsql-general
On Sat, Sep 25, 2010 at 3:12 PM, rey <reywang@optonline.net> wrote:
> On 09/25/2010 10:03 AM, Tom Lane wrote:
>>
>> rey<reywang@optonline.net>  writes:
>>
>>>
>>> Why limit this to a single character?
>>>
>>
>> Performance.  Believe it or not, breaking fields at the delimiter is
>> a significant factor in COPY speed.
>>
>>                        regards, tom lane
>>
>>
>
> True, but just for 5% to 10% degradation here.
> For RDBMS, correct indexes and good logical design we are talking about 10
> times or more performance gains.
>
> Who cares about 10% waste here? Is it Oracle and other commercial RDBMS no
> such limitation.

Believe it or not, data loading performance is one of the most common
standard metrics people used to benchmark databases.  A large class of
applications need to slam data in the db as quickly as possible, do
some work, and slam it out/dump it.  Copy performance matters.

merlin

pgsql-general by date:

Previous
From: Andrew Hunter
Date:
Subject: Re: "IN" in a geometric database using data type "point"
Next
From: A B
Date:
Subject: Re: Index on points