configure a database to use asynchronous data writes – whereby modified or new data are held in the memory cache for periodic flushing to disk by the operating system's I/O subsystem. The common term for classic-super comparison table. Moved a number of sections on installing, working with databases, and (un)safety into newly created top-level sections. 2.2.1 22 Dec 2005 PV Corrected statement on SS thread usage section. Added a subsec- tion on DISTINCT. Changed “More about NULLs” subsection some- what. Renamed “Safety measures” to “Preventing data loss”. The Security subsection has been moved elsewhere. Extended Backup

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 MON$MEMORY_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FLOAT data type has an approximate precision of 7 digits after the decimal point. To ensure the safety of storage, rely on 6 digits. 3.2.2. DOUBLE PRECISION The DOUBLE PRECISION data type is stored that the memory allocated for storing the return value will be freed after the function is executed. It is used only if the memory was allocated dynamically in the UDF. In such a UDF, the memory must be

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757 MON$MEMORY_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . approximate precision of 7 decimal digits after the decimal point (24 binary digits). To ensure the safety of storage, rely on 6 decimal digits of precision. The syntax FLOAT(bin_prec) was introduced in wasted space of a 3KB blob on page size 4096 with one on 32768: +/- 1KB vs +/- 29KB), and increase memory consumption of the page cache. LENGTH Clause specifying the maximum size of the primary or secondary

-219 335544395 relnotdef Table is not defined -239 335544691 cache_too_small Insufficient memory to allocate page buffer cache -260 335544690 cache_redef Cache redefined -281 335544637 no_stream_plan lignment Datatype misalignment. The attempted to read or write a value that was not stored on a memory boundary. -901 335544770 exception_array_bounds_exceeded Array bounds exceeded. The code attempted requirements of the runtime stack have exceeded the memory available to it. -901 335544782 exception_sigsegv Segmentation Fault. The code attempted to access memory without priviledges. -901 335544783 exception_sigill

logb_small Log block too small at offset %ld in log file %s -239 335544691 cache_too_small Insufficient memory to allocate page buffer cache -239 335544693 log_too_small Log size too small -239 335544694 partition_too_small -901 336723998 gsec_op_specified Operation already specified -901 336920607 gstat_sysmemex System memory exhausted -901 336330783 gbak_db_info_failed gds_$database_info failed -901 336723999 gsec_pw_specified Firebird 2.0 Error Codes SQLCODE GDSCODE SYMBOL TEXT -901 335740993 gfix_mem_exhausted Virtual memory exhausted -901 336330818 gbak_open_error Cannot open status and error output file %s -901 335740994

logb_small Log block too small at offset @1 in log file @2 -239 335544691 cache_too_small Insufficient memory to allocate page buffer cache -239 335544693 log_too_small Log size too small -239 335544694 partition_too_small -901 336723998 gsec_op_specified Operation already specified -901 336920607 gstat_sysmemex System memory exhausted -901 336330783 gbak_db_info_failed gds_$database_info failed -901 336723999 gsec_pw_specified maximum size -901 335740992 gfix_corrupt_pool Corrupt pool -901 335740993 gfix_mem_exhausted Virtual memory exhausted -901 336330817 gbak_open_bkup_error Cannot open backup file @1 -901 335740994 gfix_bad_pool

........................................................................................ 696 MON$MEMORY_USAGE .......................................................................................... Класс ошибок HY (условия CLI- specific) HY000 CLI-specific condition Условия CLI-specific HY001 Memory allocation error Ошибка выделения памяти HY003 Invalid data type in application descriptor установлен сейчас HY012 Invalid transaction operation code Неверный код транзакции операции HY013 Memory management error Ошибка управления памятью HY014 Limit on the number of handles exceeded Достигнут

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681 MON$MEMORY_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54023 Too many arguments SQLCLASS HY (CLI-specific Condition) HY000 CLI-specific condition HY001 Memory allocation error HY003 Invalid data type in application descriptor HY004 Invalid data type HY007 sequence error HY011 Attribute cannot be set now HY012 Invalid transaction operation code HY013 Memory management error HY014 Limit on the number of handles exceeded HY015 No cursor name available

allocated to store (cache) database pages in memory to help improve the efficiency of the database performance. It is far quicker to read data from memory that it is to have to physically read the data Database Write Mode Many operating systems employ a disk cache mechanism. This uses an area of memory (which may be part of your server’s overall RAM or may be built into the disk hardware) to buffer

51 COUNT ===================== 42 Current memory = 19570960 Delta memory = 0 Max memory = 19652528 Elapsed time = 0.001 sec Buffers = 2048 Reads = 0 Writes = 0 Fetches