| From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
|---|---|
| To: | Carlo Stonebanks <stonec(dot)register(at)sympatico(dot)ca> |
| Cc: | 'Brian Hurt' <bhurt(at)janestcapital(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: commit so slow program looks frozen |
| Date: | 2006-10-26 04:21:50 |
| Message-ID: | 20061026042150.GD26892@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Oct 25, 2006 at 04:32:16PM -0400, Carlo Stonebanks wrote:
> >> I have a question for you: did you have a long running query keeping open
> a transaction? I've just noticed the same problem here, but things cleaned
> up immediately when I aborted the long-running transaction.
>
> No, the only processes are from those in the import applications themselves:
> short transactions never lasting more than a fraction of a second.
Do you have a linux/unix machine you could reproduce this on?
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Hamill | 2006-10-26 08:58:27 | VACUUMs take twice as long across all nodes |
| Previous Message | Jim C. Nasby | 2006-10-26 03:34:48 | Re: Best COPY Performance |