two questions:
I thought copy was for multiple rows - is its setup cost effective for one row?
copy would also only be good for insert or select, not update - is this right?
--- On Mon, 6/27/11, Pavel Stehule wrote:
From: Pavel Stehule
Subject: Re: [SQL] best performance for simple dml
To: "che
Hello
try it and you will see. Depends on network speed, hw speed. But the most
fast is using a COPY API
http://www.postgresql.org/docs/9.0/interactive/libpq-copy.html
Regards
Pavel Stehule
2011/6/27 chester c young
> what is the best performance / best practices for frequently-used simple
what is the best performance / best practices for frequently-used simple dml,
for example, an insert
1. fast-interface
2. prepared statement calling "insert ..." with binary parameters
3. prepared statement calling "myfunc(..." with binary parameters; myfunc takes
its arguments and performs an in
