| From: | david(at)lang(dot)hm |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: performance for high-volume log insertion |
| Date: | 2009-04-21 06:07:56 |
| Message-ID: | alpine.DEB.1.10.0904202305470.12662@asgard.lang.hm |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 20 Apr 2009, Stephen Frost wrote:
> Greg,
>
> * Greg Smith (gsmith(at)gregsmith(dot)com) wrote:
>> The win from switching from INSERT to COPY can be pretty big, further
>> optimizing to BINARY you'd really need to profile to justify.
>
> Have you done any testing to compare COPY vs. INSERT using prepared
> statements? I'd be curious to know how those compare and against
> multi-value INSERTS, prepared and unprepared.
and this is the rest of the question that I was trying (unsucessfully) to
ask.
is this as simple as creating a database and doing an explain on each of
these? or do I need to actually measure the time (at which point the
specific hardware and tuning settings become an issue again)
David Lang
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2009-04-21 06:41:38 | Re: performance for high-volume log insertion |
| Previous Message | david | 2009-04-21 06:05:33 | Re: performance for high-volume log insertion |