Re: performance for high-volume log insertion - Mailing list pgsql-performance

From Glenn Maynard
Subject Re: performance for high-volume log insertion
Date
Msg-id bd36f99e0904221920s6cca4c31oe766d32cd8b91723@mail.gmail.com
Whole thread Raw
In response to Re: performance for high-volume log insertion  (Stephen Frost <sfrost@snowman.net>)
Responses Re: performance for high-volume log insertion
List pgsql-performance
On Wed, Apr 22, 2009 at 9:48 PM, Stephen Frost <sfrost@snowman.net> wrote:
> Erm..  Prepared queries is about using PQexecPrepared(), not about
> sending a text string as an SQL EXECUTE().  PQexecPrepared takes an
> array of arguments.  That gets translated into a Bind command in the
> protocol with a defined number of parameters and a length for each
> parameter being passed.  That removes any need for scanning/parsing the
> string sent to the backend.  That's the savings I'm referring to.

I'd suggest this be mentioned in the sql-prepare documentation, then,
because that documentation only discusses using prepared statements to
eliminate redundant planning costs.  (I'm sure it's mentioned in the
API docs and elsewhere, but if it's a major intended use of PREPARE,
the PREPARE documentation should make note of it.)

--
Glenn Maynard

pgsql-performance by date:

Previous
From: Stephen Frost
Date:
Subject: Re: performance for high-volume log insertion
Next
From: david@lang.hm
Date:
Subject: Re: performance for high-volume log insertion