Re: COPY with hints, rebirth

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <simon(at)2ndQuadrant(dot)com>
Cc: <heikki(dot)linnakangas(at)enterprisedb(dot)com>,<noah(at)leadboat(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY with hints, rebirth
Date: 2012-03-03 20:48:16
Message-ID: 4F522F300200002500045EFD@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Simon Riggs wrote:
> Kevin Grittner wrote:
>> Simon Riggs wrote:
>>
>>> I like Marti's idea. At present, making his idea work could
>>> easily mean checksums sink

>> For my part, improving bulk load performance and TRUNCATE
>> transactional semantics would trump checksums

> It doesn't look like it needs to be either-or.

Great news!

> Please review the safe_truncate.v2.patch and
> copy_autofrozen.v359.patch, copied here to assist testing and
> inspection.

I'll look at it today.

> At present those patches handle only the TRUNCATE/COPY optimisation
> but we could easily add CTAS, CREATE/COPY, CLUSTERVACUUM FULL etc..

CREATE/COPY would be important so that pg_dump | psql -1 would
benefit.

-Kevin

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2012-03-03 20:49:00 poll: CHECK TRIGGER?
Previous Message Jeff Janes 2012-03-03 20:22:59 tuplesort memory usage: grow_memtuples