On Mon, 2003-02-24 at 07:22, Christoph Haller wrote:
> I've noticed subsequent executions of the same insert command are slow.
> I've searched the list archives for this matter and found several
> entries
> related, including suggestions how to speed up.
> The standard answer from the core team is, use COPY.
> Sorry, but this is from an application point of view not really an
> option
> if you're dealing with program variables.

What do you mean by "program variables"? If you're just referring to
variables in the programming language the DB client is written in, I see
no reason why you couldn't use COPY to input those.

> The key word REPEATED directs INGRES to encode the INSERT and save its
> execution plan when it is first executed. This encoding can account for
> significant performance improvements on subsequent executions of the
> same INSERT.

As Tom mentioned, we already support PREPARE/EXECUTE for this
functionality -- but I'd suspect that for most INSERT queries, the
parsing/rewriting/planning stages are relatively inexpensive, and the
bulk of the runtime is spent in the executor (and writing WAL records,
etc). So my guess would be that you won't see that much of a performance
improvement from this...


Neil Conway <[EMAIL PROTECTED]> || PGP Key ID: DB3C29FC

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Reply via email to