Re: COPY with hints, rebirth

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "Noah Misch" <noah(at)leadboat(dot)com>
Cc: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY with hints, rebirth
Date: 2012-03-02 23:15:47
Message-ID: 4F5100430200002500045E86@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:

> I like Marti's idea. At present, making his idea work could easily
> mean checksums sink, so not sure whether to attempt to make that
> work in detail.

For my part, improving bulk load performance and TRUNCATE
transactional semantics would trump checksums. If we have to defer
one or the other to a later release, I would prefer that we bump
checksums.

While I understand the desire for checksums, and understand others
have had situations where they would have helped, so far I have yet
to run into a situation where I feel they would have helped me. The
hint bit and freeze issues require ongoing attention and have real
performance consequences on a regular basis. And closing the window
for odd transactional semantics on TRUNCATE versus DELETE of all
rows in a table would be one less thing to worry about, in my world.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2012-03-02 23:33:41 Re: Command Triggers, patch v11
Previous Message Simon Riggs 2012-03-02 22:46:32 Re: COPY with hints, rebirth