Re: raw output from copy

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Pavel Golub <pavel(at)microolap(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: raw output from copy
Date: 2015-07-02 13:08:07
Message-ID: 559537B7.7010807@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 07/02/2015 09:02 AM, Andrew Dunstan wrote:
>
> On 07/02/2015 07:14 AM, Pavel Stehule wrote:
>> Hi
>>
>> I'll do it today evening
>>
>>
>
> Pavel,
>
> Please don't top-post on the PostgreSQL lists. You've been around here
> long enough to know that bottom posting is our custom.
>
> I posted a patch for this in 2013 at
> <http://www.postgresql.org/message-id/50F2FA92.9040000@dunslane.net>
> but it can apply to a SELECT, and doesn't need COPY. Nobody seemed
> very interested, so I dropped it. Apparently people now want something
> along these lines, which is good.

For reference, here's the Wayback Machine's version of the original blog
post referred to:
<http://web.archive.org/web/20110916023912/http://people.planetpostgresql.org/andrew/index.php?/archives/196-Clever-trick-challenge.html>

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-07-02 13:12:37 Re: drop/truncate table sucks for large values of shared buffers
Previous Message Heikki Linnakangas 2015-07-02 13:08:03 Re: drop/truncate table sucks for large values of shared buffers