Re: Processing a work queue
| От | John D. Burger |
|---|---|
| Тема | Re: Processing a work queue |
| Дата | |
| Msg-id | 02E41FE2-7896-478A-8ED7-0BEDCFC0E940@mitre.org обсуждение исходный текст |
| Ответ на | Re: Processing a work queue ("John D. Burger" <john@mitre.org>) |
| Ответы |
Re: Processing a work queue
|
| Список | pgsql-general |
I wrote: > I use a variant of The Tom Lane Solution previously pointed to, > your Plan 1 is very similar. Hmm, per that pointed-to post: http://archives.postgresql.org/pgsql-general/2003-05/msg00351.php I decided to run a periodic vacuum on my work queue. Lo and behold, I get this: ERROR: tuple concurrently updated In addition, all of my workers locked up, apparently indefinitely. I presume this was because I was foolishly doing VACUUM FULL, which locks the table. But what exactly was going on? Why did my workers hang? Thanks in advance, I am new to all this concurrency stuff ... - John Burger MITRE
В списке pgsql-general по дате отправления: