Issue 1546263: Segfaults with concurrent sqlite db access and schema change (original) (raw)

Issue1546263

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification

Title:	Segfaults with concurrent sqlite db access and schema change
Type:	Stage:
Components:	Extension Modules	Versions:	Python 2.5

process

Status:	closed	Resolution:	wont fix
Dependencies:		Superseder:
Assigned To:	ghaering	Nosy List:	ghaering
Priority:	normal	Keywords:

Created on 2006-08-24 21:17 by ghaering, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg60994 - (view)	Author: Gerhard Häring (ghaering) *	Date: 2006-08-24 21:17
This was submitted with the pysqlite tracker: http://initd.org/tracker/pysqlite/ticket/170 It can lead to segfaults in some cases when schema changes happen at critical points in time. It's a very exotic bug that you can only trigger with very unusual database access patterns (running lots and I mean lots of database schema changes while other threads/processes access the database). But it's a segfault problem nonetheless and I'd like to fix it before Python 2.5 final. It should not be a showstopper, though. I'm busy right now, but I will attack this problem early next week.
msg63077 - (view)	Author: Gerhard Häring (ghaering) *	Date: 2008-02-27 20:03
See http://initd.org/tracker/pysqlite/ticket/170 and http://initd.org/tracker/pysqlite/changeset/301
msg64658 - (view)	Author: Gerhard Häring (ghaering) *	Date: 2008-03-28 23:40
Long fixed in 2.6 and 3.0 branches. Don't think it's worth fixing it in 2.5.

History
Date	User	Action	Args
2022-04-11 14:56:19	admin	set	github: 43893
2008-03-28 23:40:57	ghaering	set	status: open -> closedresolution: wont fixmessages: +
2008-02-27 20:03:43	ghaering	set	messages: +
2006-08-24 21:17:34	ghaering	create