4
------- 1.1.01 RC - 2010-06-11
6
RN1/17: Fixed bug #430637: 'ERROR -86: Too many threads' reported during concurrecy test. I have removed the maximum thread limit. The system variable pbxt_max_threads has been depricated, and will no longer be supported in 1.1.
8
RN1/16: Added system variable pbxt_index_dirty_threshold. This is a percentage value. When the number of dirty pages in the index cache reaches this level, all indices are flushed. The default value is 80. The value 0 indicates that the indices should only be flushed when no cache pages can be freed.
10
RN1/15: Implemented re-write flushing option. Re-write flushing can be more efficient because it causes more sequential writing and less random seek operations on file flush.
12
RN1/14: Implemented asynchronous flushing of files during checkpoint. This allows multiple files (current limit 10) to be flushed at the same time, which increases the total throughput on the disk.
14
RN1/13: Added the pbxt_record_write_threshold system parameter. This value determines when the writer will start to transfer data from the transaction log to the record pointer (.xtr) and handle data (.xtd) files. The default is 4MB. If the value is set to zero then the parameter is ignored. The writer will also begin to transfer data when the transaction log cache is exhausted, or the record cache is full.
16
RN1/12: Added option to buffer and sort data written by the writer thread. This allows writes to the handle data file (.xtd) to be sorted and consolidated.
18
RN1/11: Corrected a problem that sometimes caused a pause in activity when the record cache was full.
20
RN1/10: Fixed a bug in the record cache that caused PBXT to think it had run out of cache memory. The effect was that PBXT used less and less cache over time. The bug occurs during heavy concurrent access on the record cache. The affect is the PBXT gets slower and slower.
22
RN1/9: PBXT now commits every 10000 rows during an import. Import is done during ALTER TABLE, CREATE INDEX, LOAD DATA INFILE, REPAIR TABLE, OPTIMIZE TABLE and DROP INDEX statements.
24
RN1/8: Temporary tables changes: Index files of temporary tables are no longer flushed, on recovery temporary tables are ignored.
26
RN1/7: Indexes are no longer locked during index flush. This is done by copying index pages before modification, if a flush is in progress.
28
RN1/6: Added a compile option to compact indexes where data is mainly appended to the end of the index.
30
RN1/5: Changes to index flushing:
31
- Implemented flushing of index as a background task. Several threads can wait for the index flush to complete. Threads can be notified when it is safe to continue (i.e. when all pages have been marked clean).
32
- Increased the size of the page sort buffer used to sort pages to be written to the index file.
33
- Added an option to fill pages (in the case of consecutive pages) written to the index. An option also allows the block size written to the index cache to be changed. Note that performance tests (on Mac) show no overall improvement here, flush is faster, but more data is written.
34
- Flush the index file after dirty index pages have been marked clean, this allows work to continue during flushing, in low-memory situations.
35
- Added an option to write only the area of an index page that has changed.
36
- When out of index cache, we now check other tables to see if the index cache needs to be flushed. This is not done if more than 1/4 of the entire index cache is dirty due to the current index. Tables are sorted, the one with the most dirty index pages is flushed first.
37
- When out of index cache, if less than 1/4 of the entire index cache is dirty then no flushing is done. This can happen if another thread has cleaned the cache in the meantime.
39
RN1/4: Added try lock variation for R/W locks (required to fix deadlock RN1/3).
41
RN1/3: Fixed a deadlock that could occur during low index cache situations and added some checks for index corruption.
43
RN1/2: Added thread pool for executing asynchronous tasks.
45
RN1/1: Added memory resident tables. You can create a memory resident table using "STORAGE MEMORY", for example:
47
CREATE TABLE t1 (�) ENGINE=PBXT STORAGE MEMORY
49
------- 1.0.11-7 Pre-GA - 2010-09-09
51
RN336: Compiled and tested with MySQL 5.1.50.
53
RN335: Fixed bug #523994: Deleting all records does not update table statistics.
55
RN334: Made a change to reduce the time that only temporary tables exist during the ALTER TABLE and REPAIR TABLE statements. This increases the chance of recovery if a crash occurs during these operations.
57
RN333: Log name of table when PBXT recovers an index on startup. If an error occurs during index recovery, the index is set to "repair pending".
59
RN332: Fixed an inifinite loop when a record in a row is corrupt. Added logging and set the table to "repair pending" in this case.
61
RN331: Fixed bug #626890: Crash on truncate table operation.
63
RN330: Added additional checks for corruption of the index free list.
65
------- 1.0.11-6 Pre-GA - 2010-07-08
67
RN329: Fixed bug #601245: make fails. PBXT did not compile if the partition engine was disabled in the MySQL build.
69
------- 1.0.11-5 Pre-GA - 2010-06-18
71
RN328: Fixed bug #595478: Compile fails (1.0.11-4).
73
------- 1.0.11-4 Pre-GA - 2010-06-15
75
RN327: Fixed a bug that caused a crash during delete on the index. The crash occurred due to memory overwrite when a long key is promoted after a shorter key is deleted, and the difference causes a node size overflow.
77
------- 1.0.11-3 Pre-GA - 2010-06-11
79
RN326: Fixed bug #587740: pbxt-1.0.11-pre2-ga first time create partition table error. This was not a new bug. The problem was the PBXT system table's .frm files are corrupted when the first PBXT table created is a partition table.
81
RN325: Fixed the "to-sweep" column output in xtstat.
83
------- 1.0.11-2 Pre-GA - 2010-05-26
85
RN324: Fixed bug #584070:pbxt-1.0.11-pre-ga does not work with mysql 5.1.47. This bug fix removes a hack which was done to avoid running into the LOCK_plugin lock.
87
------- 1.0.11-1 Pre-GA - 2010-05-19
89
RN323: Detect corruption of a key length in an index page. This bug fix avoids a possible crash due to index page corruption.
91
------- 1.0.11 Pre-GA - 2010-05-11
93
RN322: Creating a table the references a non-existing table can now only be done if you set: foreign_key_checks = 0. Also fixed a failure when creating tables with recursive foreign key declarations.
95
RN321: Added "Extended record count" to the CHECK TABLE output. This indicates the number of records that have a data log component.
97
RN320: All tests now run with MySQL 5.1.46.
99
------- 1.0.10n RC4 - 2010-04-28
101
RN319: Fix RN1/3 and RN1/4 back-ported from 1.1: Fixed a deadlock that could occur during low index cache situations and added some checks for index corruption, and added the try lock variation for R/W locks.
103
RN318: Fixed a bug in the atomic R/W lock. This bug occurred on multi-core Linux when under extrem load. The affect was that an index lookup could fail. The index was not corrupted.
105
------- 1.0.10m RC4 - 2010-03-29
107
RN317: This change prevents a unscheduled checkpoint from occurring when the sweeper has work to do. Checkpoint required due to the Checkpoint threshold reached are done as usual.
109
------- 1.0.10k RC4 - 2010-03-29
111
RN316: Set the maximum delay, while waiting for previous transactions to commit to 1/100s. This situation occurs when cleanup begins of a long running transaction.
113
RN315: Fixed a bug that could lead to a data log error, for example: Data log not found: '.../dlog-129602.xt'. This error occurred after a duplicate key error, dending on the table structure, because the row buffer was not restored after writing an extended record.
115
RN314: Server startup time could be very long when data logs become large because the log size was not save in the header when a data log is full.
117
------- 1.0.10j RC4 - 2010-03-24
119
RN313: Fixed an error in the calculation of the handle data record (.xtd files) size when AVG_ROW_LENGTH is set explicitly to a value less than 12. For example:
122
id int(10) unsigned NOT NULL,
123
objdata mediumblob NOT NULL,
125
) ENGINE=PBXT AVG_ROW_LENGTH=10
127
This table definition previously lead to corruption of the table because the handle data record was set to 24 (14+10), which is less than the minimum (for variable length records) handle data record size of 26.
129
This minimum consists of 14 byte record header and 12 bytes reference to the extended record data (the part of the record in the data log).
131
Tip: when setting AVG_ROW_LENGTH you should normally add 12 to the average row length estimate to ensure that the average length part of the record is always in the handle data file. This is important, for example if you wish to make sure that the rows used to build indexes are in the handle data file. CHECK TABLE tells you how many rows are in the "fixed length part" of the record (output in MySQL error log). In the example above, this would be AVG_ROW_LENGTH=17.
133
The maximum size of a field can be calculated adding the maximum byte size as described here: http://dev.mysql.com/doc/refman/5.1/en/storage-requirements.html, and then add the following values, depending on the byte size:
135
byte size <= 240, add 1
136
byte size < 2^16 (65536), add 3
137
byte size < 2^24 (16777216), add 4
138
byte size > 2^24, add 5
140
------- 1.0.10i RC4 - 2010-03-17
142
RN312: Fixed bug #534361: Valgrind error: write of uninitialised bytes in xt_flush_indices()
144
RN311: Fixed ilog corruption when running out of disk space during an index flush operation, which lead to corruption of the index.
146
------- 1.0.10h RC4 - 2010-02-25
148
RN310: Fixed Windows atomic INC/DEC operations, which lead to atomic R/W lock not working correctly. The result was that some index entries were not foound.
150
RN309: Fixed a bug that caused a crash when the index was corrupted. The crash occurs if the index page in not completely written, and an item in the index has a bad length.
152
RN308: Fixed bug #509803: can't run tpcc (cannot compare FKs that rely on indexes of different length).
154
------- 1.0.10g RC4 - 2010-02-11
156
RN307: 2010-02-15: Set the internal version number 1.0.10g.
158
RN306: All tests now run with MySQL 5.1.42.
160
RN305: Fixed a bug that could cause a crash in filesort. The problem was that the return row estimate was incorrect, which caused the result of estimate_rows_upper_bound() to overflow to zero. Row estimate has been changed, and no longer takes into account deleted rows (so the row estimate is now a maximum).
162
RN304: Fixed bug #513012: On a table with a trigger the same record is updated more than once in one statement
164
------- 1.0.10f RC4 - 2010-01-29
166
RN303: Fix RN1/10 back-ported from 1.1: Fixed a bug in the record cache that caused PBXT to think it had run out of cache memory. The effect was that PBXT used less and less cache over time. The bug occurs during heavy concurrent access on the record cache. The affect is the PBXT gets slower and slower.
168
RN302: Fix RN1/11 back-ported from 1.1: Corrected a problem that sometimes caused a pause in activity when the record cache was full.
170
------- 1.0.10e RC4 - 2010-01-25
172
RN301: Fixed index statistics calculation. This bug lead to the wrong indices being selected by the optimizer because all indices returned the same cost.
174
RN300: Fixed bug #509968: START TRANSACTION WITH CONSISTENT SNAPSHOT breaks transactional flow.
176
RN299: Fixed bug #509218: Server asserts with Assertion `mutex->__data.__owner == 0' failed on high concurrency OLTP test.
178
------- 1.0.10d RC4 - 2010-01-11
180
RN298: Fixed a bug that caused huge amounts of transaction log to be written when pbxt_flush_log_at_trx_commit = 2.
182
------- 1.0.10c RC4 - 2009-12-29
184
RN297: Updated "LOCK TABLES ... READ LOCAL" behavior to be more restrictive and compatible with InnoDB
186
RN296: Fixed bug #499026: START TRANSACTION WITH CONSISTENT SNAPSHOT does not work for PBXT
188
------- 1.0.10 RC4 - 2009-12-18
190
RN295: PBXT tests now all run with MySQL 5.1.41.
192
RN294: Fixed bug #483714: a broken table can prevent other tables from opening
194
RN293: Added system variable pbxt_flush_log_at_trx_commit. The value of this variable determines whether the transaction log is written and/or flushed when a transaction is ended. A value of 0 means don't write or flush the transaction log, 1 means write and flush and 2 means write, but do not flush. No matter what the setting is choosen, the transaction log is written and flushed at least once per second.
196
------- 1.0.09g RC3 - 2009-12-16
198
RN292: Fixed a bug that resulted in 2-phase commit not being used between PBXT and the binlog. This bug was a result of a hack which as added to solve a problem in an pre-release version of MySQL 5.1. The hack was removed.
200
------- 1.0.09f RC3 - 2009-11-30
202
RN291: Fixed bug #489088: On shutdown MySQL reports: [Warning] Plugin 'PBXT' will be forced to shutdown.
204
RN290: Fixed bug #345524: pbxt does not compile on 64 bit windows. Currently atomic operations are not supported on this platform.
206
RN286: Fixed a bug introduced in RN281, which could cause an index scan to hang. The original change was to prevent a warning in Valgrind.
208
RN285: Merged changes required to compile with Drizzle.
210
RN284: Fixed bug that cause the error "[ERROR] Invalid (old?) table or database name 'mysqld.1'", when running temp_table.test under MariaDB (thanks to Monty for his initial bug fix). Added a fix for partition table names as well.
212
RN283: Added win_inttypes.h to the distribution. This file is only required for the Windows build.
214
RN282: Fixed bug #451101: jump or move depends on uninitialised value in myxt_get_key_length
216
RN281: Fixed bug #451080: Uninitialised memory write in XTDatabaseLog::xlog_append
218
RN280: Fixed bug #451085: jump or move depends on uninitialised value in my_type_to_string
220
RN279: Fixed bug #441000: xtstat crashes with segmentation fault on startup if max_pbxt_threads exceeded.
222
------- 1.0.09e RC3 - 2009-11-20
224
RN278: Fixed compile error with MySQL 5.1.41.
226
------- 1.0.09d RC3 - 2009-09-30
228
RN277: Added r/o flag to pbxt_max_threads server variable (this fix is related to bug #430637)
230
RN276: Added test case for replication on tables w/o PKs (see bug #430716)
232
RN275: Fixed bug #430600: 'Failed to read auto-increment value from storage engine' error.
234
RN274: Fixed bug #431240: This report is public edit xtstat fails if no PBXT table has been created. xtstat now accepts --database=information_schema or --database=pbxt. Depending on this setting PBXT will either use the information_schema.pbxt_statistics or the pbxt.statistics table. If information_schema is used, then the statistics are displayed even when no PBXT table exists. Recovery activity is also displayed, unless pbxt_support_xa=1, in which case MySQL will wait for PBXT recovery to complete before allowing connections.
236
RN273: Fixed bug #430633: XA_RBDEADLOCK is not returned on XA END after the transacting ended with a deadlock.
238
RN272: Fixed bug #430596: Backup/restore does not work well even on a basic PBXT table with auto-increment.
240
------- 1.0.09c RC3 - 2009-09-16
242
RN271: Windows build update: now you can simply put the pbxt directory under <mysql-root>/storage and build the PBXT engine as a part of the source tree. The engine will be linked statically. Be sure to specify the WITH_PBXT_STORAGE_ENGINE option when running win\configure.js
244
RN270: Correctly disabled PBMS so that this version now compiles under Windows. If PBMS_ENABLED is defined, PBXT will not compile under Windows becaause of a getpid() call in pbms.h.
246
------- 1.0.09 RC3 - 2009-09-09
248
RN269: Implemented online backup. A native online backup driver now performs BACKUP and RESTORE DATABASE operations for PBXT. NOTE: This feature is only supported by MySQL 6.0.9 or later.
250
RN268: Implemented XA support. PBXT now supports all XA related MySQL statements. The variable pbxt_support_xa determines if XA support is enabled. Note: due to MySQL bug #47134, enabling XA support could lead to a crash.
252
------- 1.0.08d RC2 - 2009-09-02
254
RN267: Fixed a bug that caused MySQL to crash on shutdown, after an incorrect command line parameter was given. The crash occurred because the background recovery task was not cleaned up before the PBXT engine was de-initialized.
256
------- 1.0.08c RC2 - 2009-08-18
258
RN266: Updated BLOB streaming glue, used with the PBMS engine. The glue code is now identical to the version of "1.0.08-rc-pbms" version of PBXT available from http://blobstreaming.org/download.
260
RN265: Changes the sequential reading of data log files to skip gaps, instead of returning EOF. This ensures that extended data records are preserved even when something goes wrong with the way the file is written.
262
RN264: Fixed a bug that cased an "Data log not found" error after an out of disk space error on a log file. This bug is similar to RN262 in that it allows "gaps" to appear in the data logs.
264
RN263: Updated xtstat to compile on Windows/MS Visual C++.
266
RN262: Merged changes for PBMS version 0.5.09.
268
RN261: Concerning bug #377788: Cannot find index for FK. Fixed buffer overflow which occurred when the error was reported.
270
RN260: Fixed bug #377788: Cannot find index for FK. PBXT now correctly uses prefix of an index to support FK references (e.g. if key = (c1, c2) then an index on (c1, c2, c3) will work). Also fixed buffer overflow, which occurred when reporting the error.
272
RN259: Fixed bug #309424: xtstat doesn't use my.cnf. You can now add an [xtstat] section to my.cnf, for use with xtstat.
274
RN258: updated xt_p_join implementation for Windows to check if a thread has already exited or has not yet started
276
RN257: Removed false assertion that could fail during restore if a transaction log page was zero-filled
278
RN256: Update datalog eof pointer only if write opearions were sucessful
280
RN255: Added re-allocation of of filemap if allocating the of the new map failed. This often happens if there's not enough space on disk.
282
RN254: When a table with a corrupted index is detected, PBXT creates a file called 'repair-pending' in the pbxt directory, with the name of the table in it. Each table in the file is listed on a line by itself (the last line has no trailing \n). When the table is repaired (using the REPAIR TABLE command), this entry is removed from the file.
284
RN253: Use fcntl(F_FULLFSYNC) instead of fsync on platforms that support it. Improper fsync operation was presumably the reason of index corruption on Mac OS X.
286
RN252: Fixed bug #368692: PBXT not reporting data size correctly in information_schema.
288
------- 1.0.08 RC2 - 2009-06-30
290
RN251: A Windows-specific test update, also removed false assertion that failed on Windows.
292
RN250: Fixed a bug that caused recovery to fail when the transaction log ID exceeded 255. The problem was a checksum failed in the log record.
294
RN249: Fixed bug #313176: Test case timeout. This happened because record cache pages where not properly freed and as soon as cache filled up the performacne degraded.
296
RN248: PBXT now compiles and runs with MySQL 5.1.35. All tests pass.
298
RN247: Fixed bug #369086: Incosistent/Incorrect Truncate behavior
300
RN246: Fixed bug #378222: Drop sakila causes error: Cannot delete or update a parent row: a foreign key constraint fails
302
RN245: Fixed bug #379315: Inconsistent behavior of DELETE IGNORE and FK constraint.
304
RN244: Fixed a recovery problem: during the recovery of "record modified" action the table was updated before the old index entries were removed; then the xres_remove_index_entries was supplied the new record which lead to incorrect index update.
306
RN243: Fixed a bug that caused a recovery failure if partitioned pbxt tables where present. This happended because the recovery used a MySQL function to open tables and the PBXT handler was not yet registered
308
RN242: Fixed a bug that caused a deadlock if pbxt initialization failed. This happened because pbxt ceanup was done from pbxt_init() with PLUGIN_lock being held by MySQL which lead to a deadlock in the freeer thread
310
RN241: Fixed a heap corruption bug (writing to a freed memory location). It happened only when memory mapped files were used leading to heap inconsistency and program crash or termination by heap checker. Likely to happen right after or during DROP TABLE but possible in other cases too.
312
RN240: Load the record cache on read when no using memory mapped files.
314
RN239: Added PBXT variable pbxt_max_threads. This is the maximum number of threads that can be created PBXT. By default this value is set to 0 which means the number of threads is derived from the MySQL variable max_connections. The value used is max_connections+7. Under Drizzle the default value is 500.
316
RN238: Added an option to wait for the sweeper to clean up old transactions on a particular connection. This prevents the sweeper from getting too far behind.
318
RN237: Added an option to lazy delete fixed length index entries. This means the index entries are just marked for deletion, instead of removing the items from the index page. This has the advantage that an exclusive lock is not always required for deletion.
320
RN236: Fixed bug #349177: a bug in configure.in script.
322
RN235: Fixed bug 349176: a compiler warning.
324
RN234: Completed Drizzle integration. All Drizzle tests now run with PBXT.
326
RN233: Fixed bugs which occur when PBXT is used together with PBMS (BLOB Streaming engine).
328
RN232: Merged Drizzle-specific changes into the main tree.
330
RN231: Fixed a bug that caused bad performance as the number of threads increased. This occurred when the number of open table handles exceeded 'table_open_cache', and MySQL started closing open table handlers. PBXT was flushing a table when all table handlers were closed. PBXT will now only do this when the FLUSH TABLES statement is used.
332
RN230: Improved efficiency of conflict resolution: Implemented a queue for threads waiting for a lock. Threads no longer poll to take a lock. If a temp lock is granted because of an update, then the thread granted the temp lock will also wait for the transaction that did the update to quit.
334
RN229: Fixed bug #313391: LOAD DATA ... REPLACE broken.
336
RN228: Fixed bug #341115: 'Out of memory' error (a bug in key comparison algorithm).
338
RN227: Changed conflict handling to use spin locks and improve efficiency.
340
RN226: Fixed bug #340316: Issue with bigint unsigned auto-increment field.
342
RN225: Fixed bug #308557: UPDATE fails to match all rows in a transactional scenario.
344
RN224: Fixed a deadlock which could occur during table scans.
346
RN223: Index scans now use handles to cache buffers instead of making a copy of the index page. The handles are "copy-on-write".
348
RN222: Fixed a bug that caused the server to hang on startup if PBXT ran out of record cache while waiting for the sweeper to complete.
350
RN221: Fixed an index recovery bug. This occurred if the server crashed after operating in low index cache sitations.
352
RN220: Improved index selectivity estimation: added scanning from the end of index backwards.
354
RN219: Fixed a problem: during intersected range scan not all fields were returned by engine to MySQL.
356
RN218: Changed the way row locking (used by SELECT FOR UPDATE) works. Previously we locked a group of rows at once (although there were many groups). However, this caused conflicts even when the same rows were not locked. We now locks individual rows.
358
RN217: Fixed bug #315564: Rollbacked inserts remain permanently in table.
360
RN216: Added lock tracing. In DEBUG mode, each thread has a list of locks (semaphores, mutexes, r/w locks that it holds).
362
RN215: Fixed a bug that caused a crash during restart if an index file was flushed during recovery.
364
RN214: Fixed bug #310184: Deadlock when trying to wake up transactions
366
RN213: Fixed an index corruption bug on SPARC Solaris. Note this error will occur on any machine that does not use the x86 (little endian) byte order.
368
------- 1.0.07 RC - 2008-12-15
370
RN212: Fixed build problems on NetBSD.
372
RN211: Fixed build problems on FreeBSD.
374
RN210: Fixed build problems on OpenSolaris.
376
RN209: Added handling of the foreign_key_checks system flag.
378
RN208: xtstat will now automatically reconnect if the connection to server is lost.
380
RN207: Foreign key references are now checked on CREATE TABLE.
382
RN206: Fixed a crash if inserting into a table that has an FK that references a column that has no index on it.
384
RN205: Added processing of foreign key action SET DEFAULT.
386
RN204: Fixed an index recovery problem: unswept index entries were not recovered correctly
388
RN203: Fixed foreign key bug: REPLACE fails with 'on delete cascade'
390
RN202: Fixes and updates to tests, now all tests pass on windows and linux.
392
RN201: Fixed ref-counting for mmapped files.
394
RN200: Fixed an index recovery problem: unswept index entries were not recovered correctly .
396
RN199: Recovery now takes place on plug-in startup. Previously recovery occurred when the first PBXT table was accessed.
398
RN198: Fixed a recovery bug that caused index entries to get out of sync with the data file.
400
RN197: Improved the efficiency of group commit.
402
RN196: Changed checkpointing so that it now works during idle time. Every record, row or index file fllush now also contributes to the checkpoint (fuzzy checkpointing). Checkpointing is forced to complete after about 50% of the checkpoint threshold in order to ensure the correct maximum for log reading on recovery.
404
RN195: Fixed scheduling bug that caused sweeper to get behind with the cleanup, which caused performance problems in high conflict situations. Foreground threads will now wait if the sweeper gets too far behind.
406
RN194: Created the xtstat program which monitors the internal performance of PBXT. Run xtstat --help for more details information of the output.
408
RN193: Implemented the pbxt.statistics virtual table. The statistics table returns information about the internal activity of the engine. This includes I/O byte counts, cache hit counts and usage, commit count, etc.
410
RN192: Due to timing issues in the engine API it could happen that the client received an OK for a committed transaction before the transaction was actually committed. This problem has been fixed.
412
RN191: Fixed a bug that caused a hang when conflicts occured while reading a covering index.
414
RN190: Previously the sweeper delayed deletion of transaction structures until all transactions that were running during sweeping have quit. This is now handled by the same code that fixed the bug in RN189.
416
RN189: Fixed a bug that could cause a row to go missing due to a visibility issue.
418
RN188: Fixed a bug which ocurred when using CREATE TABLE ... AVG_ROW_LENGTH=x, and the table contained BLOBs. In this case, alter table corrupted the table.
420
RN187: Windows now stores paths in the location file in UNIX format by converting all '\' characters to '/'. Note that the location file is only cross-platform if the paths are relative (which is the default).
422
RN186: Set version number to 1.0.07.
424
------- 1.0.06 Beta 2 - 2008-11-06
426
RN185: Disabled support for INSERT DELAYED because of MySQL bug #40505
428
RN184: Implemented info(flag == HA_STATUS_AUTO) engine API call. This call returns the next value that will be assigned as auto-increment value on the table.
430
RN183: Turned off streaming on Windows (see XT_STREAMING macro in sources)
432
RN182: Switch code base to the latest version of BLOB streaming engine (PBMS): www.blobstreaming.org.
434
RN181: Updated pbxt-test-run default parameters (--force is on, --default-storage-engine is pbxt, --base-dir is set according to config)
436
RN180: PBXT can now cope with a missing .xti file (the file that contains the table indexes). This file can be regenerated using REPAIR TABLE.
438
RN179: On recovery PBXT now creates a filed called 'recovery-progress' in the pbxt database. The recovery percentage complete is written to this file as recovery progresses. Note that this file will not be created if no recoery is necessary or if PBXT estimates that it will read less then 10MB to do recovery.
440
RN178: Fixed a problem in CHECK TABLE that caused memory corruption for fixed-size records
442
RN177: Added "crash debugging". When enabled, crash debugging does the following:
443
- Create a core dump on Windows if the server crashes.
444
- Make a backup copy of the datadir directory before recovery if the server crashes.
445
- Keep at least 5 of the previous transaction logs.
446
Currently crash debugging is disabled by default. To disable, create a file called 'no-debug' in the pbxt database folder, and restart the server. When crash debugging is disabled by default, it can be enabled by creating a file called 'crash-debug; in the pbxt database folder.
448
RN176: Fixed a bug: a lock was not released appropriately
450
RN175: Fixed some debug assertions
452
RN174: Fixed some of test/mysql-test tests
454
RN173: Fixed a RENAME TABLE bug, that prevented index files from being properly recreated
456
RN172: Added the file ./pbxt/lock-pid. This file is locked while the server is running, and contains the process of the server. PBXT will return an error on startup if the file is locked or the process is still running in order to prevent a second server from being started.
458
RN171: Implemented the AVG_ROW_LENGTH table attribute. When set, this value determines the size of the fixed length data component of a record. Normally this size is estimated depending on the column definitions. The command CHECK TABLE dumps the current average row length to the log. This can be used to find a suitable value for AVG_ROW_LENGTH.
460
RN170: Changed configure so that debug/optimize flags set for building the engine override the flags set for MySQL. If --with-debug is not specified, then the engine will use the flags set when building MySQL. If MySQL was built with --with-debug=full, the DEBUG will be defined for the engine. When building the engine, the following flags can be set:
461
yes - Debug symbols enabled, no optimization, DEBUG not defined.
462
full - Debug symbols enabled, no optimization, DEBUG defined.
463
only - Debug symbols enabled, MySQL flags used, DEBUG not defined.
464
prof - Profile code enabled, optimization on, DEBUG not defined.
465
no - No debug symbols, optimization on, DEBUG not defined.
467
RN169: Used MySQL root Makefile instead of config.status in order to extract settings (such as CFLAGS and CXXFLAGS) for the PBXT build.
469
RN168: Fixed Windows build after merging changes for Drizzle.
471
RN167: Fixed "This table requires primary key" error in sql-bench.
473
RN166: Fixed threading problems that caused crashes in sql-bench.
475
RN165: Added sql-bench to pbxt source tree.
477
RN164: Ported PBXT to Drizzle. To compile for Drizzle DRIZZLED must be defined on the command line. The -drz.am and -drz.in files are must be used when PBXT is embedded in Drizzle.
479
RN163: Added "make test" build step. Running "make test" from the root of pbxt source tree will launch test/mysql-test/pbxt-test-run.pl with appropriate options to execute the pbxt functional test suite. On Windows where
480
pbxt is statically linked into mysql server binary pbxt testing works by going to test/mysql-test directory and running ./pbxt-test-run.pl with --base-dir argument pointing to a mysql source tree (mysql binaries are taken
481
from there) and passing the rest of usual arguments (--force --mysqld=--default-storage-engine=pbxt)
483
RN162: The 'pbxt' database must now be dropped explicitly. It is automatically created when the first PBXT table is created. After that, the pbxt database can be dropped once all PBXT tables have been dropped. Dropping the pbxt database will also cause all transaction (pbxt/system directory) and data logs (pbxt/data directory) to also be deleted.
485
RN161: Added pbxt.location system table. This table can only be dropped when all PBXT tables have been deleted. Dropping the system table will cause all transaction (pbxt/system directory) and data logs (pbxt/data directory) to also be deleted.
487
RN160: Made changes to run with MySQL 6.0.6.
489
RN159: Changes to configure: added --with-plugindir=<path>, which should be used to specify the plugin directory. This means that --libdir should no longer be used. For backwards compatibility configure will still recognize this options if the path ends with 'plugin'.
491
Also updated --help, to include all options, and better desciptions of the options.
493
The configure options are now as follows:
495
--with-mysql=<path> - (Required) It specifies the path to the MySQL source tree. The source should already be built. All other options will be taken from the MySQL build by default.
496
--with-debug=yes/no - (Optional) Specify if then engine should be built with different debug options to the MySQL source tree.
497
--with-plugindur=<path> - (Optional) Specify an alternative installation directory for the plugin. By default it will be installed in the plugin directory of the MySQL installation.
500
RN158: Added support for core dumps on Windows. This can be enabled by defining XT_COREDUMP. On by default at the moment. If the server crashes a file called PBXTCore00000001.dmp will be created in the data directory. This file can be openned using MS VS.
502
RN157: Fixed a compile problem with tv_nsec which is not supported on all platforms.
504
RN156: Updated tests to run with MySQL 5.1.28.
506
RN155: Errors during cascade update of VARCHAR values with trailing spaces
508
RN154: Fixed a bug: impossible to create a foreign key that referenced an ENUM or SET column
510
RN153: Fixed a bug that caused the following problems: #1. Foreign keys: crash if update cascade and autocommit=0 #2. Foreign keys: crash if update cascade and multi-level recursion
512
RN152: Fixed missing information about foreign keys in I_S.table_constraints and I_S.referential_constraints
514
------- 1.0.05 Beta - 2008-08-30
516
RN151: "Quick config": It is now possible to configure the engine by just specifying the mysql source code tree (the --with-mysql option). The --libdir and --with-debug setting will be deduced automatically.
518
RN150: Added system variable pbxt_sweeper_priority, 0 = low (default), 1 = normal (same as user threads), 2 = high. The sweeper cleans up deleted records (deleted records also result from an update). If allowed to accumulate, these records can slow searches. Higher priority for the sweeper is recommended on systems with 4 or more cores.
520
RN149: Record cleanup is now initiated if a deleted record is found, and the transaction that deleted the record has ended. Since waking up the sweeper is an expensive operation, normally the sweeper will run every 1/10th of a second.
522
RN148: Fixed a bug which caused transaction starvation (one transaction was constantly locked out) during high conflict updates. This lead to cleanup of records not being done, which lead to a general slow down.
524
RN147: Fixed a problem with TRUNCATE TABLE: a failed TRUNCATE TABLE could put the engine into an invalid state that later caused a crash
526
RN146: Fixed a bug that caused the error: "-49: Record format unknown, either corrupted or upgrade required".
528
RN145: Added pbxt_db_offline_log_function system variable, 0 = recycle logs (default), 1 = delete logs (default on Mac OS X), 2 = keep logs.
530
------- 1.0.04 Alpha - 2008-08-02
532
RN144: Completed port and testing of Windows version.
534
RN143: Fixed a bug which caused the free-er thread to hang. This was a result of an invalid operation ID, which was the result of the checkpointer flushing the table at the same time as a foreground thread.
536
RN142: The fast RW/mutex lock can now handle nested calls. This is possible during a sequential scan.
538
RN141: The normal behavior in MySQL is that an auto-increment values will be re-issued if you delete the row containing the current maximum auto-increment value and then restart the server. To prevent this you can use ALTER TABLE my_table AUTO_INCREMENT = <current-max-auto-increment> + 1, before deleting the current maximum auto-increment value.
540
A new system variable, pbxt_auto_increment_mode, has been added so that this work around is not necessary. When set to 0 (the default), auto-increment works as described above. When set to 1, the AUTO_INCREMENT value of the table is automatically to prevent previously issued auto-increment values being returned.
542
However, if the server crashes, a gap of up to 100 unique values can result, because the table AUTO_INCREMENT value is incremented in steps of 100.
544
RN140: Index statistics are now automatically recalculated when the table row count exceeds 200.
546
RN139: Fixed a bug that caused index corruption, error: "int idx_push(index_xt.cc:172) -2: Core B-tree too deep".
548
RN138: Handle startup and recovery when an index is corrupted.
550
RN137: Fixed a bug in the zero wait R/W lock that caused the lock to fail (the state is extremely volatile, and must be written to memory after increment).
552
RN136: Fixed a bug that cause the error "int xt_pwrite_file(filesys_xt.cc:789) errno (14): Bad address".
554
RN135: Fixed TRUNCATE TABLE that did not work correctly when the table contained BLOBs stored in the BLOB streaming engine (www.blobstreaming.org).
556
RN134: Fixed a bug that caused duplicate rows to be returned from an index scan (using a SELECT FOR UPDATE) if a concurrent update was done.
558
RN133: Optimised PBXT for multi-processor scale-up. This mostly involved using different types of locks instead of the standard pthread mutex and reader/writer locks [TODO: 0038].
560
------- 1.0.03 Alpha - 2008-05-30
562
RN132: Fixed bug when using PBXT in conjunction with the BLOB streaming engine (www.blobstreaming.org). Uploaded BLOBs could not be inserted into a table.
564
RN131: Fixed wait for background processes on shutdown. Shutdown will wait a maximum of 16 seconds for each process.
566
RN130: Fixed calculation of bytes to be read for recovery.
568
RN129: Fixed bug in cleanup of unterminated transactions.
570
RN128: The writer will now start working when one of the following is true:
571
- it is time for a checkpoint,
572
- the log cache is almost full,
573
- the free'er is waiting for the writer,
574
- there is no other activity.
576
RN127: Fixed checkpoint frequency. Checkpointing is now done correctly after 'pbxt_checkpoint_frequency' bytes.
578
RN126: Implemented index consistent write [TODO: 0050].
580
RN125: Implemented memory mapping for row pointer (.xtr) and handle data files (.xtd).
582
RN124: Index files now use direct I/O.
584
------- 1.0.02 Alpha - 2008-04-25
586
RN123: Fixed compile errors with MySQL 5.1.24.
588
------- 1.0.01 Alpha - 2008-03-28
590
RN122: ++++ NOTE: This version is not compatible with older versions of PBXT ++++.
592
RN121: Transaction logs are now global so that multi-database statements are now possible. This makes it also possible to work PBXT temporary tables.
594
RN120: Transaction logs pre-allocated and recycled.
596
RN119: Transaction log writes on 512 byte boundaries only.
598
------- 1.0.00 Alpha - 2008-03-10
600
This version has alpha status because of the large number of changes done for full durability.
602
RN118: ++++ NOTE: This version is incompatible to older versions of PBXT ++++.
604
RN117: Documentation now avaliable at http://www.primebase.org/documentation.
606
RN116: Corrected the plug.in file so that PBXT compiles when dropped into the storage directory in the MySQL source tree.
608
RN115: Compiled and tested with MySQL 5.1.23.
610
RN114: Increased index block size. Minimum is now 4K. Default is 16K.
612
RN113: Calculate index selectivity to return a more accurate value from records_in_range(). NOTE: FLUSH TABLESl will update the index statistics, after data has been inserted or updated.
614
RN112: Optimized table storage, saving 8 bytes per row.
616
RN111: Optimized search on keys containing 2 or 3 not null integer values.
618
RN110: Optimization: store the row ID in the index so that an index entry can be verified as current without loading the record. This is necessary to optimize an access with index coverage.
620
RN109: Optimization: only load the record extended data if required.
622
RN108: Implemented SHOW ENGINE PBXT STATUS;
624
RN107: Added the following system variables:
626
pbxt_index_cache_size - The amount of memory allocated to the index cache, used only to cache index data
627
pbxt_record_cache_size - The amount of memory allocated to the record cache used to cache table data
628
pbxt_log_cache_size - The amount of memory allocated to the transaction log cache used to cache on transaction log data
629
pbxt_log_file_threshold - The size of a transaction log before rollover, and a new log is created
630
pbxt_transaction_buffer_size - The size of the global transaction log buffer (the engine allocates 2 buffers of this size)
631
pbxt_log_buffer_size - The size of the buffer used to cache data from transaction and data logs during sequential scans, or when writing a data log
632
pbxt_checkpoint_frequency - The amount of data written to the transaction log before a checkpoint is performed
633
pbxt_data_log_threshold - The maximum size of a data log file
634
pbxt_garbage_threshold - The percentage of garbage in a data log file before it is compacted
636
RN106: PBXT now compiles for MySQL 6.0.3.
638
RN104: Updates now locks a record temporarily. This prevents most "record changed" errors, however, it makes UPDATE statements a type of "committed read". This means that you may update a different value to that which you selected in repeatable read mode. To avoid this, use SELECT FOR UPDATE if you plan to UPDATE records after reading.
640
RN103: Implemented SELECT FOR UPDATE. This is implemented by turning SELECT FOR UPDATE into a type of "committed read". This means that, if you do a SELECT followed by a SELECT FOR UPDATE you can get different results, even in repeatable read mode.
642
RN102: Implemented recovery of index entries. Note: indexes are not yet fully consistent. This means that index can become currupted due to a crash. Data, however, cannot be lost. The indices can be rebuild using REPAIR TABLE.
644
RN101: Writing and flushing of a single transaction write-ahead log.
646
RN100: Automatic rollover of transaction logs as they become full.
648
RN99: Implementation of the transaction log cache.
652
RN97: Implementation of the writer thread that applies changes in the transaction log to the database.
654
RN96: Implementation of the checkpointer thread that periodically flushes the database and writes a checkpoint which determines the recovery start point.
656
RN95: Implementation of the free'er thread that is responsible for keeping the record cache at a preset level.
658
RN94: Modifications to the record cache so that rows are stored in pages, in order to speed up sequence access.
660
RN93: Implemented the recovery process which applies changes written to the log that are not in the database, on startup.
662
RN92: Modification of the sweeper thread which cleans up rolled-back transactions and deleted data, to use the new transaction log format.
664
RN91: Modifications to the data logs so that they use the same record structure as the transaction logs.
666
RN90: The data logs are now managed "per database" in order to minimize the work done to flush and commit a transaction.
668
RN89: Implementation of a file handle pool for the data logs.
670
------- 0.9.91 Beta - 2007-10-30
672
RN88: The format of the URL genearated by MyBS has been changed. The format of the BLOB URLs is now as follows:
674
'~*' <db-name> '/' <type-char> <table-id> '-' <blob-id> '-' <access-code> '-' <server-id>
676
Where <type-char> is '_' or '~'.
678
Examples: ~*test/_11-128-fbd590b-0, ~*test/~1-524-3dc45b09-0
680
In other words, the characters '>' has been replace by '*', '^' has been replace by '_' and ':' has been replace by '~'. The reason for this is that the characters '>' and '^' are not allowed in URLs, and must be URL-encoded. The character ':' is reserved, but allowed.
682
NOTE: This change makes this version incompatible with previous versions of MyBS. If you have a table with BLOB URLs, you can upgrade the URLs as follows:
684
UPDATE blob_table SET blob_col = REPLACE(REPLACE(blob_col, '~>', '~*'), '/:', '/~');
686
Replacing '^' is not necessary because BLOB URLs with '^' should not appear in tables.
688
------- 0.9.90 Beta - 2007-10-17
690
RN87: Corrected stack trace of errors passed through the BLOB streaming API.
692
RN86: Added new engine API accessor functions that appeared in 5.1.21 (thanks Stewart).
694
RN85: Added plug.in file. PBXT now compiles when dropped into the storage directory of the MySQL build tree. However, you have rebuild configure. For example:
696
rm -rf autom4te.cache/
702
./configure --with-plugins=max --without-innodb --prefix=/usr/local/mysql --with-debug=full
704
NOTE: ./configure --help should show that the PBXT has been included.
706
RN84: Fixed several problems with shutdown of PBXT in combiniation with MyBS.
708
------- 0.9.89 Beta - 2007-08-17
710
RN83 (2007-08-21): Fixed a crash due to a compile bug that does not like the contruct *((xtWordPS *) &(v)) = (xtWordPS) (x) (macro allocr_() and alloczr_()).
712
RN82: It is now possible to insert non-URL values into a LONGBLOB field, in the previous version the generated an "Invalid URL" error. Such values can be retrieved as a stream using a field reference.
714
RN81: Fixed a bug that caused PBXT to crash during certina operations when MyBS was not installed.
716
RN80: Set engine as capable of row-level replication, but not as statement replication. Statement replication does not work because MVCC is not serializable.
718
------- 0.9.88 Beta - 2007-07-25
720
RN79: Made some corrections in order to compile with MySQL 5.1.20.
722
RN78: Support for the features of the MyBS BLOB Streaming engine, version 0.5 Alpha.
724
RN77: Bugfix: The server crashes during BLOB data handling. The reason is the table field structure is shared, and may not be changed.
726
------- 0.9.87 Beta - 2007-06-19
728
RN76: The major feature of this release is support for the BLOB Streaming Engine. The current version enables the download of specific BLOB columns via the Streaming Engine. For example:
731
CREATE TABLE notes_tab (
732
n_id INTEGER PRIMARY KEY,
735
INSERT notes_tab VALUES (1, "This is a BLOB streaming test!");
739
http://localhost:8080/test/notes_tab/n_text/n_id=1
741
will return the value "This is a BLOB streaming test!"
743
RN75: Bugfix: MySQL prints error: "Plugin 'PBXT' will be forced to shutdown". This error was caused by the plug-in having a reference to itself.
745
RN74: Added system variable pbxt_index_cache_size and pbxt_record_cache_size. These variable can now be set on the mysqld command line (for example: --pbxt_record_cache_size=50MB). The values are also displayed by SHOW VARIABLES.
747
------- 0.9.86 Beta - 2007-04-07
749
RN74: ++++ NOTE: This version is incompatible to older versions of PBXT ++++.
751
In order to upgrade, install the older version of PBXT. Convert all tables to MyISAM using ALTER TABLE t1 ENGINE=MyISAM. Then install the new version of PBXT and convert back using ALTER TABLE t1 ENGINE=PBXT.
753
RN73: Each table will now use a maximum of 4 data log files. This means a maximum of 7 files per table. The minimum is 3 for tables that do not have a variable field that exceeds about 40 bytes in size. This means that under Linux PBXT requires a maximum of 7 file handles per table used. Windows lock of pread/pwrite (atomic seek and read/write) functions means it requires a file handler per file per open table handler. [TODO: 0044]
755
RN72: All threads now write to the same data log file. Recovery and compaction take this fact into account. Each thread still writes its own transaction log.
757
RN71: Removed all directory scans when creating and dropping table. Increased the table limit to 10000.
759
RN70: Changed locking to avoid a deadlock when TRUNCATE TABLE is used together with other DML.
761
RN69: procedures and functions are now considered atomic, and execute in a single transaction.
763
RN68: Bug fixed: all files are now correctly flushed before commit.
765
------- 0.9.85 Beta - 2007-03-15
767
RN67: Changed the implementation of the pushsr_ and allocr_ macros because "*((void **) &(v) = " caused a crash due to a compiler error on some platforms (thanks Luciano for your help on this one and RN66).
769
RN66: Fixed a bug that caused PBXT to corrupt the index file when the size exceeded 4GB. [TODO: 0031]
771
RN65: PBXT now runs under Windows. This source tree must be placed in the MySQL source storage directory in order to compile. Further details of how to build are in the windows-readme.txt file. [TODO: 0027]
773
RN64: Improved speed of table lookup by ID after a table has been deleted. The sweeper needs to ignore these records. Scanning the directory each time was too slow.
775
RN63: Added checking for repeat update of a record in a statement.
777
RN62: Committed read no longer blocks due to a change made by another transaction (the XT_REPEATABLE_READ_BLOCKS define, turns blocking on).
779
RN61: Avoid checking for duplicates if an index is not modified by an update.
781
RN60: Records updated repeatedly by a transaction are now updated in place. [TODO: 0040]
783
------- 0.9.8 Beta - 2007-01-30
785
RN59: Reduced the number of file handles used to a maximum of one per file. This assumes that pread() and pwrite() allows multiple threads to use the same file handle (according to my tests, this is the case).
787
RN58: Added the configure flag --with-debug=only which compiles a version of the plug-in with debug symbols that will link to an non-debug MySQL server.
789
RN57: Changed error number returned on lock from 1205 (lock timeout) to 1020 (optimistic lock failure).
791
RN56: Added UNIX environment variable for PBXT system parameters. These must be set before starting mysqld, for example:
793
setenv pbxt_index_cache_size 400MB
794
setenv pbxt_record_cache_size "1 GB"
796
Values are in bytes unless one of the following units is specified: GB, MB, Kb
798
RN55: Fixed a bug which prevented VARCHAR values from being compressed correctly when stored in variable length rows.
800
RN54: Fixed a bug which caused a crash when PBXT was used with MySQL 5.1.14. This bug also caused data to be corrupted on insert.
802
RN53: Set query caching mode to transactional. [TODO: 0027]
804
RN52: Added conditions so that the engine compiles with MySQL 5.1.14 and 5.1.13.
806
------- 0.9.74 Beta - 2006-12-14
808
RN51: DELETE FROM <table>; is no longer implemented by re-creating the table. This statement now works by deleting all rows. TRUNCATE is implemented as before, by re-creating the table.
810
RN50: The test scripts innodb.test and innodb-mysql.test have been modified to run with PBXT.
812
RN49: [TODO: 0020] Implemented foreign keys. Functionality is identical to InnoDB with 2 exceptions:
814
* Data types of referenced columns must be an exact match (e.g. you cannot mix VARCHAR and CHAR values).
815
* Currently an exact matching index is required on referenced columns (i.e. the index may not have more columns that the columns used in the foreign key definition).
817
Also note the following:
819
* It is possible to create foreign keys that reference non-existent tables or columns. An error will occur when updating a table with an incorrect foreign key declaration.
820
* If you alter the data-type of a column referenced by a foreign key set you need to set foreign_key_checks=0; or an error will occur.
822
RN48: Fixed a bug in the implementation of indexes on ENUM and SET types.
824
RN47: Fixed a bug that caused a crash when an index was place on a BLOB column, and data was retrieved from the index directly.
826
------- 0.9.73 Beta - 2006-10-31
828
RN46: Updated test scripts to run with MySQL 5.1.13.
830
------- 0.9.72 Beta - 2006-10-19
832
RN45: Corrected compilation errors that occurred due to a change to struct st_mysql_plugin.
834
------- 0.9.71 Beta - 2006-10-04
836
RN44: Corrected compilation errors that occurred due to changes in the storage engine API.
838
------- 0.9.7 Beta - 2006-09-20
840
RN43: This is the first Beta release of PrimeBase XT. It has been integrated into MySQL 4.1.21 and is available as a plug-in for MySQL 5.1.12, or later. This version has been extensively tested using mysql-test-run, on various Linux and Mac OS X platforms.
842
RN42: ++++ NOTE: This version is incompatible to older versions of PBXT ++++. Files created by older versions cannot be opened by version 0.9.7.
844
RN41: Renaming or deleting a table while using a name with different case to the original created name did not work.
846
RN40: Fixed a bug when grouping and searching on indexed columns that contain a null.
848
RN39: Fixed bugs related to trailing spaces on VARCHAR values. Values that only vary by the number of trailing spaces (for example "aa" and "aa "), are now correctly handled as identical.
850
RN38: The default AUTO_INCREMENT value was not correctly preserved during ALTER TABLE.
852
RN37: Created a MySQL 5.1 Plugin version of PBXT. [TODO: 0017]
854
RN36: Fixed a race condition in the row cache which had the affect that inserted rows dissappeared after cleanup because the cache was out of date. I was only able to reproduce this error on multi-processor machines.
856
------- 0.9.6 - 2006-08-05
858
RN35: ++++ NOTE: This version is incompatible to older versions of PBXT ++++.
860
The disk format of tables and log files has changed slightly in this version. As a result, files created by older versions cannot be opened by version 0.9.6. An error will be generated. If you have data wish to preserve, first start the older version of XT and convert all tables to MyISAM. The stop the server and removed all transaction log file (files of the form xtlog-*.xt). Then start the new version and convert tables back to XT.
862
RN34: Implemented READ COMMITTED transaction mode. XT now supports READ COMMITTED and SERIALIZABLE transaction modes. NOTE: if the mode is set to REPEATABLE READ, SERIALIZABLE is used. If the mode is set to READ UNCOMMITTED READ COMMITTED is used.
864
RN33: The implementation of AUTO_INCREMENT on a paritial index is non-standard. A unique value is generated without regard to the value of the index prefix. For example, assume we have the following table: CREATE TABLE t1 (c1 CHAR(10) not null, c2 INT not null AUTO_INCREMENT, PRIMARY KEY(c1, c2));
866
With the following contents: c1 c2
870
After executing the following statement: insert into t1 (c1) values ('B');
872
This is the result using PBXT: c1 c2
877
The standard result would be: c1 c2
882
RN32: PBXT does not permit access to multiple databases within a single transaction. For example:
885
update database_1.t1 set a=10;
886
update database_2.t2 set d=10;
889
In this case the following error is returned: 1015: Can't lock file (errno: -1)
891
RN31: The implementation of COUNT(*) has changed. For effectiency, rows are not counted. The information is taken from the header of the record (.xtr) files. This information is only 100% accurate after transaction cleanup has completed. Which basically means, only when PBXT is idle. ANALYZE TABLE waits for all background activity to stop, so the statement may be executed before a COUNT(*) to ensure an accurate result. NOTE: Other then waiting for background processes, ANALYSE TABLE is not implemented.
893
RN30: Two concurrency bugs have been fixed: a shared lock was used instead of an exclusive lock when deleting from a transaction list, the transaction segment semaphore was not initialized. XT now runs correctly in a multi-processor environment. The test used was sysbench on a dual-process, dual-core, AMD 64-bit machine running SUSE Linux 10.0.
895
RN29: PBXT compiles and runs on under 64-bit Lunix. [TODO: 0009]
897
RN28: ./mysql-test-run --force --mysqld=--default-storage-engine=pbxt will now execute most tests successfully. Changes to the tests and the result have been documented in http://www.primebase.com/xt/download/pbxt-test-run-changes.txt. [TODO: 0004, 0019]
899
RN27: Fixed a bug that caused the server to crash if when using tables locks and transactions. For example: LOCK TABLES, BEGIN, COMMIT, SELECT. This sequence now returns an error. The correct sequence is:
901
LOCK TABLES, BEGIN, COMMIT, UNLOCK TABLES, SELECT
903
LOCK TABLES, BEGIN, COMMIT, BEGIN, SELECT COMMIT, UNLOCK TABLES
905
RN26: Fixed a concurrency problem which caused a number of threads to hang during the sysbench test - see RN30 above (bug reported by Vadim).
907
RN25: Fixed a bug that caused the server to hang when ha_pbxt::create() and ha_pbxt::ha_open() where given different, but equivalent paths for a particular table.
909
RN24: Fixed bug in the indexing of blob columns, for example: create table t1(name_id int, name blob, INDEX name_idx (name(5)));
911
RN23: When a duplicate key error occurs in auto-commit mode, the transaction is now rolled back.
913
RN22: Fixed incorrect duplicate key error. In the case of a unique key which allows NULLs, duplicates are allowed if the inserted key contains a NULL. For example:
915
create table t1 (id int not null, str char(10), unique(str));
916
insert into t1 values (1, null),(2, null),(3, "foo"),(4, "bar");
918
RN21: PBXT now returns the correct error code on duplicate key: 1062 instead of 1022.
920
RN19: Implemented AUTO_INCREMENT on partial keys. However, the XT implementation is non-standard. Increment of partial index works, but the ID generated is incremented like a non-partial index. For example:
922
create table t1 (c1 char(10) not null, c2 int not null auto_increment, primary key(c1, c2));
928
insert into t1 (c1) values ('B');
935
The standard result would be:
941
RN18: Implemented TRUNCATE TABLE and DELETE FROM <table>; (i.e. a DELETE without WHERE clause). Previously DELETE FROM <table>; did not cause an error, but no rows where deleted (TRUNCATE TABLE returned an error). [TODO: 0012, 0022]
943
RN17: Implemented CREATE TABLE (...) auto_increment=<value>;
945
------- 0.9.51 - 2006-07-06
947
RN16: Fixed crash which could occur when creating the first table in a database (bug reported by Hakan).
949
------- 0.9.5 - 2006-07-03
951
RN15: This version concludes the re-structuring of the PBXT implementation. I have made a number of major changes, including:
953
- All files except the transaction logs are now associated with a particular table. All table related files begin with the name of the table. The extension indicates the function.
955
- I have merged the handle and the fixed length row data for performance reasons.
957
- Only the variable size component of a row is stored in the data log files. As a result the data logs can now be considered as a type of "overflow" area.
959
- Memory mapped files are no longer used because it is not possible to flush changes to the disk.
961
RN14: File names have the following forms:
963
[table-name]-[table-id].xtr - These files contains the table row pointers. Each row pointer occupies 8 bytes and refers to a list of records. The file name also contains the table ID. This is a unique number which is used internally by XT to identify the table.
965
[table-name].xtd - This file contains the fixed length data of a table. Each data item includes a handle and a record. The handle references a record in the data log file if the table contains variable length records.
967
[table-name].xti - This file contains the index data of the table.
969
[table-name]-[log-id].xtl - This is a data log file. It contains the variable length data of the table. A table may have any number of data log files, each with a unique ID.
971
xtlog-[log-id].xt - These files are the transaction logs. Log entries that specify updates reference a data file record. Each active thread has its own transaction log in order to avoid contension.
973
RN13: Fixed the bug "Hang on DROP DATABASE". [TODO: 0016]
975
RN12: PBXT currently only supports the "Serializable" transaction isolation level. This is the highest isolation level possible and includes the "repeatable-read" functionality [TODO: 0015]. This is implemented by giving every transaction a snapshot of the database at the point when the transaction is started.
977
If the transaction tries to update a record that was updated by some other transaction after the snapshot was taken, a locked error is returned. A deadlock can occur if 2 transactions update the same record in a different order. PBXT can detect all deadlocks.
979
RN11: I have implemented write buffering on the table data files. [TODO: 0013]
981
RN10: The unique constraint (UNIQUE INDEX/PRIMARY KEY) is now checked correctly. [TODO: 0008]
983
RN9: I have implemented a conventional B-tree algorithm for the indices (instead of the Lehman and Yoa B*-link tree). Although this reduces concurrency it improves the performance of queries significantly because of the simplicity of the algorithm. Deletion is also implemented in a very simple manner. [TODO: 0007]
985
RN8: PBXT now has only 2 caches [TODO: 0006]:
987
The Index Cache (pbxt_index_cache_size): This is the amount of memory the PBXT storage engine uses to cache index data and row pointers. This is all the data in the files with the extensions '.xti' and '.xtr'. This cache is managed in blocks of 2K.
989
The Record Cache (pbxt_record_cache_size): This is the amount of memory the PBXT storage engine uses to cache table row data (handles and records). This is all the data in the files with the extension '.xtd'.
991
The size of the caches are determined by the values of the system variables pbxt_index_cache_size and pbxt_row_cache_size. By default these values are set to 32MB.
993
RN7: Auto-increment is now implemented in memory. This is done by doing a MAX() select when a table is first opened to get the high value. After that, then high value is incremented in memory on INSERT. On UPDATE (or INSERT) the value in memory is adjusted if necessary. This method also makes it possible for rows to be inserted simultaneously on the same table. [TODO: 0005, 0014]
995
RN6: ./run-all-tests --create-options=TYPE=PBXT succeeds. [TODO: 0004]
997
RN5: Using sql-bench and my own Java based test I have confirmed that PBXT behaves correctly during multi-threaded access. [PARTIALY TODO: 0002]
999
RN4: Load/Stability test. Using sql-bench I have tested PBXT under load over a long period of time. [PARTIALY TODO: 0001]
1001
------- 0.9.2 - 2006-04-01
1003
RN3: Fixed a bug that cause the error "-6: Handle is out of range: [0:0]".
1005
RN2: Implemented SET, ENUM and YEAR data types.
1007
RN1: Fixed a bug in the error reporting when a table is created with a datatype that is not supported. [TODO: 0011]
added
removed
plugin/pbxt/ChangeLog
