| From: | Alex Pilosov <alex(at)pilosoft(dot)com> |
|---|---|
| To: | Joseph Shraibman <jks(at)selectacast(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Weird error |
| Date: | 2001-06-28 19:03:21 |
| Message-ID: | Pine.BSO.4.10.10106281502070.5536-100000@spider.pilosoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 28 Jun 2001, Joseph Shraibman wrote:
> Alex Pilosov wrote:
> >
>
> > This is definitely FALSE. Vacuum does not lock the database, it acquires
> > certain locks while its vacuuming certain tables. I.E. your clients may
> > not be able to modify table while its being vacuumed.
> >
> I've had a vacuum deadlock my database. When I killed the vacuum client
> (^C from the command line) my program continued.
Are you sure you mean 'deadlock'? Deadlock is when neither client nor
vacuum can proceed. What most likely happened is vacuum locking the table
until its done, and that is a normal behavior.
-alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Molter | 2001-06-28 19:08:41 | Re: Slower on Solaris (NOT that Red Hat thread anymore) |
| Previous Message | Vince Vielhaber | 2001-06-28 19:00:39 | Re: Repeated messages (was Re: Suggested improvement : Adjust SEQUENCES) |