SSI error messages
От | Peter Eisentraut |
---|---|
Тема | SSI error messages |
Дата | |
Msg-id | 1310707359.13354.13.camel@vanquo.pezone.net обсуждение исходный текст |
Ответы |
Re: SSI error messages
|
Список | pgsql-hackers |
Some of these new error messages from the SSI code are a mouthful: not enough elements in RWConflictPool to record a rw-conflict not enough elements in RWConflictPool to record a potentialrw-conflict These are basically "out of shared memory" conditions that could be moved to a DETAIL message. Canceled on identification as a pivot, during conflict out checking. Canceled on conflict out to old pivot %u. Canceledon identification as a pivot, with conflict out to old committed transaction %u. Canceled on conflict out to oldpivot. Canceled on identification as a pivot, during conflict in checking. Canceled on identification as a pivot,during write. Canceled on conflict out to pivot %u, during read. Canceled on identification as a pivot, duringcommit attempt. Canceled on commit attempt with conflict in from prepared pivot. These are DETAIL messages, with the rest of the report saying ERROR: could not serialize access due to read/write dependencies among transactions HINT: The transaction might succeedif retried. AFAICT, the documentation doesn't mention anything about this "pivot" that keeps coming up. Is it useful that have the user face this information? Is there anything a user can derive from seeing one of these messages versus another, and in addition to the error and hint, that would help them address the situation?
В списке pgsql-hackers по дате отправления: