Re: New kind of crash?
От | Mark Kirkwood |
---|---|
Тема | Re: New kind of crash? |
Дата | |
Msg-id | 513AA9D0.8070601@catalyst.net.nz обсуждение исходный текст |
Ответ на | New kind of crash? (Josh Berkus <josh@agliodbs.com>) |
Список | pgsql-bugs |
Do you have any non default procedural languages installed? I provoked exactly that error with a similar script which used a PL/R procedure (see BUGS thread "PL/R Median Busts Commit"...the cause is signal hi-jacking in that case). Regards Mark On 09/03/13 13:27, Josh Berkus wrote: > Folks, > > This is one I've never seen before: > > => select generate_master_tables(); > WARNING: AbortTransaction while in COMMIT state > PANIC: cannot abort transaction 9387287, it was already committed > PANIC: cannot abort transaction 9387287, it was already committed > The connection to the server was lost. Attempting reset: Failed. > Time: 42259.753 ms > !> > > Interestingly, Postges came back up on its own after about a minute and > seems to be OK. The stored procedure in question is one which creates > about 600 tables. This actually exceeds max_locks_per_transaction, but > what happened above is not the normal failure for that. > > Note that the tables were, in fact, created, and as far as I can tell > there's no corruption of the database. >
В списке pgsql-bugs по дате отправления: