Skip site navigation (1) Skip section navigation (2)

Re: [PATCH] COPY .. COMPRESSED

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] COPY .. COMPRESSED
Date: 2013-01-15 23:33:19
Message-ID: 50F5E73F.5090808@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On 01/15/2013 06:22 PM, Tom Lane wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
>> Perhaps I'm taking a bit too narrow view of the world, but my thinking
>> is OLTP won't want things compressed, as it increases latency of
>> requests, while OLAP users are operating with enough data that they'll
>> go through the effort to use COPY.
> Also, if there are so many people using COPY in their apps, why have we
> never seen any submitted patches to extend libpq with functions to
> construct/deconstruct COPY data?  Surely somebody would have said to
> themselves that they shouldn't be responsible for knowing those escaping
> rules.

There are perfectly good libraries in Perl and other languages for 
constructing/deconstructing CSV data. If we didn't have CSV 
import/export I suspect we would have heard lots more howls by now.

cheers

andrew


In response to

pgsql-hackers by date

Next:From: Michael PaquierDate: 2013-01-15 23:48:16
Subject: Re: pg_ctl idempotent option
Previous:From: Andres FreundDate: 2013-01-15 23:26:01
Subject: Re: Curious buildfarm failures (fwd)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group