MySQL 4.1 and 5.0: Prepared Statement Leaks
by Jeremy Cole on Thursday, March 30th, 2006 at 15:44:49 in MySQLDiscount Tramadol UltramUltram 50 MgUltram PriceBuy Generic UltramUltram PrescriptionCheapest UltramUltram Vs VicodinEr Recall UltramUltram 50mgUltram IngredientDiscount UltramUltram Drug TestUltram NarcoticUltram Addiction StoryHigh UltramUltram OverdoseUltram OvernightUltram DosageUltram DrugDay Next UltramBuying Ultram100 Er UltramCheap Ultram OnlinePain UltramInfcom.it Ultram Ultram.htmlPregnancy UltramAlcohol UltramUltram Without A PrescriptionUltram MedicineUltram Withdrawal SymptomUltram TabletTramadol Ultram InfoUltram Weight LossUltram Non NarcoticUltram MexicoBlog Inurl P UltramUltram And DepressionUltram An OpiateSnorting UltramUltram PharmacyCheap Ultram PrescriptionComing Off UltramUltram And ZoloftOnline Ultram Prescription06 59 UltramDetox For UltramUltram DoseDrug Information UltramOrder Ultram OnlineUltram Pain Reliever
As it turns out, the memory leaks which I initially blamed on 5.0 also affect 4.1. It’s not stored procedures leaking memory as I initially thought, but server-side prepared statements. The problem was finally worked out by setting useServerPrepStmts=false in the JDBC code, which “fakes” prepared statements on the client side, without any other code changes.
Read MySQL Bug #18300 for more information!
