unless you specify otherwiise, every insert carries its own transaction
begin/commit. That's a lot of overhead for a single insert, no? Why
not use a single transaction for, say, each 1000 inserts? That would
strike a nice balance of security with efficiency.
pseudo code for the insert:
Begin
local network client is a WinXP Pro, P4, 2.2 gHzthe remote network client is WinXP Pro, P4, 1.9 gHz
Lou
>>> Tom Lane <[EMAIL PROTECTED]> 3/11/2005 1:21 PM >>>
"Lou O'Quin" <[EMAIL PROTECTED]> writes:> Hi Tom. I referenced the status line of pgAdmin. Per
er to the Data Output page."
Lou>>> Tom Lane <[EMAIL PROTECTED]> 3/11/2005 12:10 PM >>>
"Lou O'Quin" <[EMAIL PROTECTED]> writes:> it appears to actually be hypersensitive to the transport delay. The => ratios of time for the data transpo
As a test, I ran a query in the pgAdmin query tool, which returns about 15K records from a PostgreSQL v8.01 table on my Win2K server.I ran the same query from the local server, from another PC on the same 100 mbit local network, and from a PC on a different network, over the internet. The times fo
