> Possibly you got bit by the recently-fixed LISTEN/NOTIFY race condition?
> http://archives.postgresql.org/pgsql-bugs/2008-03/msg00094.php
> IIRC this could only be a problem if your listener had only just started
> listening, though.
- Geez, I realize I forget to state the version I'm using: 3.1.
- I had been doing all my testing from a cold start-up. But when I go back
now and keep testing over & over, I keep seeing the problem over & over.
But
reading the re****t you linked to, it *does* seem to me like it describes
my
problem, and that it could happen any time, not just soon after starting a
listen.
If this gets fixed in a near-term release I'm good. Right now, I can
kludge
around it with a double-query of the modified table--because right now the
usage patterns are such that I don't think this will ever skip an update.
(Longer-running updates, or a heavier load, and I might have a bigger
problem.)
Four years of using PostegreSQL, and finally there's a bug that actually
affects the correct operation of my software. Not too shabby ;-)
--
Scott Ribe
scott_ribe@[EMAIL PROTECTED]
(303) 722-0567 voice
--
Sent via pgsql-general mailing list (pgsql-general@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
|
