This repository has been archived by the owner on Dec 4, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 53
/
ChangeLog-Archive
126 lines (110 loc) · 6.75 KB
/
ChangeLog-Archive
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
# DO NOT EDIT THIS FILE -- MAINTAINED AUTOMATICALLY
# This file contains past ChangeLog entries
* Mon Aug 10 2020 Ying Zhang <[email protected]> - 11.39.1-20201006
- Finished a first version of the new monitoring function
user_statistics(), which is only intended for the DBAs.
For each database user who has logged in during the current mserver5
session, it returns
"username": login name of the database user,
"querycount": the number of queries this user has executed since his/her
first login,
"totalticks": the total execution time (in microsecond) of the queries ran
by this user,
"maxquery": the query with the longest execution time (if two queries have
the same execution time, the newer overwrites the older),
"maxticks": the execution time of the 'maxquery' (in microsecond),
"started": the start timestamp of the 'maxquery',
"finished": the finish timestamp of the 'maxquery'.
* Wed Jun 10 2020 Sjoerd Mullender <[email protected]> - 11.39.1-20201006
- Removed support for LiDAR data, that is the SQL procedures
sys.lidarattach, sys.lidarload, and sys.lidarexport.
* Thu Apr 2 2020 Martin Kersten <[email protected]> - 11.39.1-20201006
- The sys.queue() has been turned into a circular buffer to allow for
inspection of both active, paused and recently executed queries.
* Mon Apr 20 2020 Sjoerd Mullender <[email protected]> - 11.37.1-20200511
- A new system to deal with debug output has been implemented. There is
now an option --dbtrace to mserver5 that takes a file argument to which
debug output is written. The default value is the file mdbtrace.log
inside the database directory. This option can also be set through
the monetdb program.
- The home directory of the automatically created monetdb user was
changed from /var/MonetDB to /var/lib/monetdb (RPM based systems
only). This home directory is (currently) not used for anything,
though.
- Python 2 support has been removed. There is now only support for
using Python 3.
* Thu Jan 30 2020 Sjoerd Mullender <[email protected]> - 11.37.1-20200511
- Removed support for bam and sam files.
* Fri Dec 6 2019 Panagiotis Koutsourakis <[email protected]> - 11.37.1-20200511
- Added mserver5 option (--set raw_strings=true|false) and monetdb
database property (raw_strings=yes|no) to control interpretation
of strings.
* Wed Oct 10 2018 Sjoerd Mullender <[email protected]> - 11.31.11-20181011
- Some subtle dependencies between RPMs have been fixed.
* Wed Feb 14 2018 Stefan Manegold <[email protected]> - 11.29.1-20180315
- mclient's execution time profiling options and output format have
been changed. Instead of implicitly via the "--interactive"/"-i"
option (or when using an interactive mclient console), execution time
profiling is now controlled via an explicit "--timer=timermode"/"-t
timermode" command-line option, or a "\t timermode" command in the
interactive mclient console. The default (also in the interactive
mclient console) is now timermode "none", i.e., no timing information
is given. Timermode "clock" activates client-side wall-clock timing
("clk") in "human-friendly" format much like the interactive mode did
before. Timermode "performance" also provides detailed server-side
timings: "sql" is the time to parse the SQL query, optimize the
logical relational plan and create the initial physical (MAL) plan;
"opt" is the time to optimize the physical (MAL) plan; "run" is the
time to execute the physical (MAL) plan. With timermode "performance"
all server-side timings and the client-side wall-clock time are given
in milliseconds (ms). Note that the client-measured wall-clock time
"clk" is reported per query only when options "--interactive" or
"--echo" are used, because only then does mclient send individual
lines (statements) of the SQL script to the server. Otherwise, mclient
sends the SQL script in large(r) batch(es) to the server, and, thus,
only the total wall-clock time per batch is measured and reported. The
server-measured detailed performance timings "sql", "opt", "run" are
always measured and reported per query. Also, all timing information
is now given on a separate line and sent to stderr rather than stdout.
* Fri Feb 9 2018 Sjoerd Mullender <[email protected]> - 11.29.1-20180315
- Some types and constants were moved from configure (and hence
monetdb_config.h) to gdk.h. In particular, the types "lng" and
"ulng" have been moved and can therefore no longer be used by code
that doesn't (ultimately) include gdk.h. Just use int64_t instead.
A bunch of format defines have been removed: SZFMT, SSZFMT, PTRFMT,
PDFMT. Just use the C standard codes for those (%zu, %zd, %p, %td).
The define for printing a lng (LLFMT) was also moved. Use PRId64 for
printing int64_t in code not using gdk.h. Removed all references to
__int64 and long long (use int64_t instead).
* Thu Apr 13 2017 Mark Raasveldt <[email protected]> - 11.27.1-20170705
- Added a new server-side protocol implementation. The new protocol
is backwards compatible with the old protocol. Clients can choose
whether they want to use the old or the new protocol during the initial
handshake with the server. The new protocol is a binary column-based
protocol that is significantly faster than the old protocol when
transferring large result sets. In addition, the new protocol supports
compression using Snappy or LZ4.
* Mon Feb 20 2017 Sjoerd Mullender <[email protected]> - 11.27.1-20170705
- Moved the sphinx extension module to its own repository.
See https://dev.monetdb.org/hg/MonetDB-sphinx/.
* Thu Feb 16 2017 Sjoerd Mullender <[email protected]> - 11.27.1-20170705
- Removed GSL module: it's now a separate (extension) package.
See https://dev.monetdb.org/hg/MonetDB-gsl/.
- The PCRE library is now optional for systems that support POSIX regular
expressions.
* Thu Jan 12 2017 Martin van Dinther <[email protected]> - 11.27.1-20170705
- Added 5 new sys schema tables: function_languages, function_types,
key_types, index_types and privilege_codes. They are pre-loaded with
static content and contain descriptive names for the various integer
type and code values. See also sql/scripts/51_sys_schema_extension.sql
* Thu Sep 22 2016 Sjoerd Mullender <[email protected]> - 11.25.1-20161214
- The Perl, PHP, and Python clients, and the JDBC driver each now have
their own repositories and release cycles. The Python client is
maintained by Gijs Molenaar on Github
(https://github.com/gijzelaerr/pymonetdb), the other clients are
maintained by CWI/MonetDB on our own server
(https://dev.monetdb.org/hg/monetdb-java,
https://dev.monetdb.org/hg/monetdb-perl,
https://dev.monetdb.org/hg/monetdb-php).
* Fri Jul 1 2016 Sjoerd Mullender <[email protected]> - 11.23.5-20160704
- Lots of memory leaks have been plugged across the whole system.