"Kevin Grittner" <kevin.gritt...@wicourts.gov> writes: > PostgreSQL is much less prone to serialization failures, but it is > certainly understandable if hot standby replication introduces new > cases of it.
In this case it will be possible to get this error even if you're just running a single SELECT query -- and that's the *only* query in the database at all. A vacuum being replayed -- even in a different database -- could trigger the error. Or with the btree split issue, a data load -- again even in a different database -- would be quite likely cause your SELECT to be killed. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
