Many years ago, I considered myself fairly expert when it came to
performance tuning and query optimization in postgresql, but I've been
hiding out inside (insert big company that doesn't use Postgresql here) for
a long while while postgresql has continued to evolve, and much has changed
since
This strikes me as something that shouldn't matter in the vast majority of
applications. Putting a bunch of logic for rendering an
application-specific format of your data in prepared statements or stored
procedures in your database violates the separation of concerns that most
folks like to
I know nothing about running PostgreSQL in windows, but slowness in
establishing connections on a particular host that isn't replicable elsewhere
is very often the result of something doing reverse DNS lookups on a server
when accepting new connections. Perhaps the client you are connecting
Start a transaction before the first insert and commit it after the last one
and it will be much better, but I believe that the copy code path is optimized
to perform better than any set of queries can, even in a single transaction
Sent from my iPhone
On Dec 10, 2011, at 5:27 PM, Jon Nelson
Sent from my iPhone
On Nov 7, 2011, at 7:21 PM, Mohamed Hashim nmdhas...@gmail.com wrote:
Hi all,
Thanks for all your responses.
Sorry for late response
Earlier we used Postgres8.3.10 with Desktop computer (as server) and
configuration of the system (I2 core with 4GB RAM) and also
