Re: Weird error
От | Joseph Shraibman |
---|---|
Тема | Re: Weird error |
Дата | |
Msg-id | 3B3BA841.972DB490@selectacast.net обсуждение исходный текст |
Ответ на | Re: Weird error (Alex Pilosov <alex@pilosoft.com>) |
Список | pgsql-general |
No, it was deadlocked. Neither vacuum nor my program were doing anything. Alex Pilosov wrote: > > 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly -- Joseph Shraibman jks@selectacast.net Increase signal to noise ratio. http://www.targabot.com
В списке pgsql-general по дате отправления: