| From: | Boris Goldowsky <boris(at)range(dot)infoplease(dot)com> |
|---|---|
| To: | pgsql-general(at)postgreSQL(dot)org |
| Subject: | concurrency |
| Date: | 1999-11-16 21:16:05 |
| Message-ID: | 14385.51605.660473.625912@griddle.infoplease.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
It seems that whenever we are doing a large operation -- eg, CREATE
INDEX on a sizable table, or VACUUM on a big database -- all other
postgres operations on that server stop dead. Attempts to do simple
operations on completely separate databases (but on the same server)
will hang (or perhaps they proceed extremely slowly) until after the large
operation is finished.
Is there any way around this limitation? Is this something that can
be addressed through parameter tweaking of the postmaster, or would it
be solved by having multiple CPUs on the database machine?
Bng
--
Boris Goldowsky Engineering & Development Manager
Information Please, LLC boris(at)alert(dot)infoplease(dot)com
www.infoplease.com 617 832-0324
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boris Goldowsky | 1999-11-16 21:20:10 | concurrency |
| Previous Message | Richard Welsh | 1999-11-16 20:41:23 | Re: [GENERAL] Re: replication |