I don't think that's the advice being looked for here - if this behaviour is repeatable, then there is something askew with the inet protocol.

What is the client application written in? Do you know what version of the postgres network protocol your driver code is using? Are the inserts inside a transaction?

I'm very interested in this issue since the environment I now work in has a lot of network connected databases and the performance is much less than I am used to with local databases.

Mark.
-- Mark Aufflick
e [EMAIL PROTECTED]
w www.pumptheory.com (work)
w mark.aufflick.com (personal)
p +61 438 700 647
On 23/07/2004, at 4:02 PM, Christopher Kings-Lynne wrote:


But with the server running on one machine and the client running on
another, the two machines being connected by a 100 Mb ethernet, with nothing
else on the network, this test takes 17 minutes to run. I have tried
changing the frequency of COMMIT operations, but with only a small effect.

Are you using separate INSERT statements? Try using COPY instead, it's much faster.


chris


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly


======================================================================= =
Pain free spam & virus protection by: www.mailsecurity.net.au
Forward undetected SPAM to: [EMAIL PROTECTED]
======================================================================= =




========================================================================
Pain free spam & virus protection by:          www.mailsecurity.net.au
Forward undetected SPAM to:                   [EMAIL PROTECTED]
========================================================================


---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Reply via email to