Re: Serialization exception : Who else was involved?
| От | Craig Ringer |
|---|---|
| Тема | Re: Serialization exception : Who else was involved? |
| Дата | |
| Msg-id | 549E83C8.4000207@2ndquadrant.com обсуждение исходный текст |
| Ответ на | Serialization exception : Who else was involved? (Olivier MATROT <olivier.matrot@accelis-sir.fr>) |
| Ответы |
Re: Serialization exception : Who else was involved?
|
| Список | pgsql-hackers |
On 12/02/2014 06:17 PM, Olivier MATROT wrote: > Serialization conflict detection is done in > *src/backend/storage/lmgr/predicate.c*, where transactions that are > doomed to fail are marked as such with *the SXACT_FLAG_DOOMED* flag. > > I simply added elog(...) calls with the NOTIFY level, each time the flag > is set, compiled the code and give it a try. I don't see how that'd necessarily correctly identify the query/queries in the other tx that're involved, though. Perhaps I'm thinking in terms of more complicated serialization failures? What sorts of failures are you actually running into? -- Craig Ringer http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: