Int32 Operation code If operation equals op_response: Int32 Object handle Int64 Object ID Buffer Data (meaning depends on the operation). Byte[] Status vector  Information about parsing the SQL response Int32 Operation code If operation equals op_sql_response: Int32 Message count Buffer Response data (meaning depends on the operation). 2.3. Fetch response Chapter 2. Responses 4 that there are no more rows. Int32 Count of rows following response  The data rows are not in a buffer as described in Data types, but as a sequence of data rows, see Reading row data. 2.4. Slice response

Codes SQLCODE GDSCODE SYMBOL TEXT 101 335544366 segment Segment buffer length shorter than expected 101 335544366 segment Segment buffer length shorter than expected 100 335544338 from_no_match No match 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 Log partition @1 -902 335544448 bad_sec_info -902 335544449 invalid_sec_info -902 335544470 buf_invalid Cache buffer for page @1 invalid -902 335544471 indexnotdefined There is no index in table @1 with id @2 -902

country || ' ' || postcode; END SUSPEND; -- the statement that sends an output row to the buffer -- and makes the procedure "selectable" END 3. With DEFINER set for procedure p, user stream is materialized completely into an internal buffer. While reading this secondary stream, a hash function is applied and a pair {hash, pointer to buffer} is written to a hash table. Then the primary Expression -> Filter -> Hash Join (inner) -> Table "STUDENTS" as "S" Full Scan -> Record Buffer (record length: 145) -> Table "CLASSES" as "C" Full Scan For a MERGE join, the plan must

Codes from msg.gbak, release sources SQLCODE GDSCODE SYMBOL TEXT 101 335544366 segment Segment buffer length shorter than expected 100 335544338 from_no_match No match for first value expression 100 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 Table is -902 335544448 bad_sec_info -902 335544449 invalid_sec_info -902 335544470 buf_invalid Cache buffer for page invalid -902 335544471 indexnotdefined There is no index in table with

country || ' ' || postcode; END SUSPEND; -- the statement that sends an output row to the buffer -- and makes the procedure "selectable" END See also CREATE OR ALTER PROCEDURE, ALTER ]] FOR UPDATE does not do what it suggests. Its only effect currently is to disable the pre-fetch buffer.  It is likely to change in future: the plan is to validate cursors marked with FOR UPDATE if  As an alternative, it may be possible in your access components to set the size of the fetch buffer to 1. This would enable you to process the currently-locked row before the next is fetched and locked

Error Codes Firebird 2.0 Error Codes SQLCODE GDSCODE SYMBOL TEXT 101 335544366 segment Segment buffer length shorter than expected 100 335544338 from_no_match No match for first value expression 100 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 Log partition %ld -902 335544448 bad_sec_info -902 335544449 invalid_sec_info -902 335544470 buf_invalid Cache buffer for page %ld invalid -902 335544471 indexnotdefined There is no index in table %s with id %d -902

at the pointer page for our table, we see the following: tux> ./fbdump ../blank.fdb -p 162 Page Buffer allocated. 4096 bytes at address 0x804b008 Page Offset = 663552l DATABASE PAGE DETAILS ===================== Min Space: 0 Max Space: 0 Page[0000]: 166 Page Buffer freed from address 0x804b008 We can see from the above this is indeed the pointer page (type 0x04) 166. If we now dump page 166 we can see the following: tux> ./fbdump ../blank.fdb -p 166 Page Buffer allocated. 4096 bytes at address 0x804b008 Page Offset = 679936l DATABASE PAGE DETAILS =====================

following: • Command line options for the gfix database utility. • Shadow file handling. • Cache and buffer handling. • Transaction management. • Cache management. • Starting and stopping a database. • the database cache is dependent on the database page size and the number of buffers allocated, a buffer is the same size as a database page, and whether the installation is using Classic or Superserver memory (which may be part of your server’s overall RAM or may be built into the disk hardware) to buffer writes to the hardware. This improves the performance of applications that are write intensive but

Firebird Database Cache Buffer Norman Dunbar, Martin Köditz Version 1.2, 28 May 2020 Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . confirmed and the DBA responsible for the database asked, on the list, how he could reduce the buffer cache as much as possible but still have a responsive system. Ann has given her permission for this MON$IO_STATS As mentioned above, the table MON$IO_STATS can be used to help you determine how well your buffer cache is performing. The table has the following structure: MONS$STAT_ID The statistic id. MONS$STAT_GROUP

Der Firebird Cache-Buffer Norman Dunbar, Martin Köditz Version 1.2-de, 28. Mai 2020 Inhaltsverzeichnis 1. Einleitung . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . oben bereits angegeben, kann die Tabelle MON$IO_STATS genutzt werden, um zu bestimmen, wie gut Ihr Buffer-Cache arbeitet. Die Tabelle hat folgende Struktur: MONS$STAT_ID Die Statistik-ID. MONS$STAT_GROUP firebirdsql.org/manual/pdl.html (HTML). Die Original-Dokumentation trägt den Titel Firebird Database Cache Buffer. Der ursprünglich Autor der Original-Dokumentation ist: Norman Dunbar unter Verwendung der durch