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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
