Re: COPY and Volatile default expressions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: COPY and Volatile default expressions
Date
Msg-id 15416.1366041306@sss.pgh.pa.us
Whole thread Raw
In response to Re: COPY and Volatile default expressions  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: COPY and Volatile default expressions
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On 15 April 2013 16:24, David Fetter <david@fetter.org> wrote:
>> Do you have numbers on this, or ways to gather same?  In other words,
>> how do we know what resources (time, CPU cycles, disk seeks, etc.) are
>> being consumed here?

> The multi-insert optimisation for COPY is already there and works well
> enough to have been committed.

You seem to not have answered the question.  Exactly what sort of
performance gain might be possible, bearing in mind that anything that
invokes a trigger (for instance) is unlikely to be amazingly fast
anyway?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: COPY and Volatile default expressions
Next
From: Simon Riggs
Date:
Subject: Re: COPY and Volatile default expressions