Re: [GENERAL] Slow network retrieves

2004-05-11 Thread wespvp
On 5/9/04 1:58 PM, "Tom Lane" <[EMAIL PROTECTED]> wrote: > I am not sure how either of these techniques map into ecpg though. > If you want to use ecpg then I'd suggest bringing up the question on > pgsql-interfaces --- the ecpg gurus are more likely to be paying > attention over there. I got som

Re: [GENERAL] Slow network retrieves

2004-05-11 Thread Gaetano Mendola
[EMAIL PROTECTED] wrote: The back end is pretty much idle. It shows 'idle in transaction'. Well, is not soo much idle, it's holding a transaction id! That "idle in transaction" is not your problem but however I suggest you take a look at why you have idle in transaction backend; do you have back

Re: [GENERAL] Slow network retrieves

2004-05-09 Thread Tom Lane
<[EMAIL PROTECTED]> writes: > On 5/9/04 9:32 AM, "Tom Lane" <[EMAIL PROTECTED]> wrote: >> Are you sure it is a network problem? > Yes, it is definitely due to the network latency even though that latency is > very small. Here it is running locally: > [ about 2 records/sec ] Okay, I just want

Re: [GENERAL] Slow network retrieves

2004-05-09 Thread wespvp
On 5/9/04 9:32 AM, "Tom Lane" <[EMAIL PROTECTED]> wrote: > Are you sure it is a network problem? What performance do you get > if you run the same test program locally on the database machine? > How about issuing the same sort of FETCH commands via a psql script? Yes, it is definitely due to the

Re: [GENERAL] Slow network retrieves

2004-05-09 Thread Tom Lane
<[EMAIL PROTECTED]> writes: > I'm seeing what seems like slow retrieval times over the network. Are you sure it is a network problem? What performance do you get if you run the same test program locally on the database machine? How about issuing the same sort of FETCH commands via a psql script?