Date: 2015-04-23 14:37:49 +0200
From: Pete Hollobon <>
To: SQL devs <>
Version: 11.19.9 (Oct2014-SP2)
CC: @njnes, pete

Last updated: 2015-06-22 22:32:20 +0200

Comment 20835

Date: 2015-04-23 14:37:49 +0200
From: Pete Hollobon <>

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36
Build Identifier:

Adding a new column and setting its NOT NULL constraint within a transaction crashes the server:

CREATE TABLE bugexample (
id INTEGER
);

START TRANSACTION;
ALTER TABLE bugexample ADD COLUMN newcolumn integer;
ALTER TABLE bugexample ALTER COLUMN newcolumn SET NOT NULL;
COMMIT;

Removing the transaction around the =ALTER TABLE= commands results it in completing correctly.

Reproducible: Always

Steps to Reproduce:

1. Run the SQL above

Actual Results:

Server crashes (SIGSEGV)

Expected Results:

Column added not null after transaction commit.

Comment 20840

Date: 2015-04-24 11:09:47 +0200
From: @njnes

test added and fixed bug by checking for existence of update bat.

Comment 20868

Date: 2015-05-15 12:50:10 +0200
From: MonetDB Mercurial Repository <>

Changeset 7fe602576cf5 made by Niels Nes niels@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7fe602576cf5

Changeset description:

added tests for bug #3715, 3718 and also output for 3720

fixed bug #3718 (ie check for unknown tables)