You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SQL front end uses the force flag in calls to BATappend and other BAT changing functions to overrule the read-only setting of the BAT because SQL maintains its own recovery mechanism. The understanding SQL has is that by appending, the already existing part of the BAT is not changed, and so recovery in the case of a crash (or just exit) before the appended data was properly committed consists of just replaying the appends (which are stored in the write-ahead log). This works fine for the most part. The string heap of string BATs don't just append, but this is already handled by the recovery code.
The problem here is that other atom heaps of variable sized atoms (e.g. BLOB) also modify more in the heap when data gets appended, and these modifications are not handled when the heap is recovered at startup.
Date: 2017-11-13 15:27:36 +0100
From: @sjoerdmullender
To: GDK devs <>
Version: 11.27.9 (Jul2017-SP2)
Last updated: 2017-12-14 14:46:00 +0100
Comment 25873
Date: 2017-11-13 15:27:36 +0100
From: @sjoerdmullender
The SQL front end uses the force flag in calls to BATappend and other BAT changing functions to overrule the read-only setting of the BAT because SQL maintains its own recovery mechanism. The understanding SQL has is that by appending, the already existing part of the BAT is not changed, and so recovery in the case of a crash (or just exit) before the appended data was properly committed consists of just replaying the appends (which are stored in the write-ahead log). This works fine for the most part. The string heap of string BATs don't just append, but this is already handled by the recovery code.
The problem here is that other atom heaps of variable sized atoms (e.g. BLOB) also modify more in the heap when data gets appended, and these modifications are not handled when the heap is recovered at startup.
Comment 25876
Date: 2017-11-14 14:44:42 +0100
From: MonetDB Mercurial Repository <>
Changeset 7253f70231be made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.
For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=7253f70231be
Changeset description:
Comment 25902
Date: 2017-11-23 14:56:33 +0100
From: @sjoerdmullender
I believe this is now fixed.
The text was updated successfully, but these errors were encountered: