The size of a database with big records becomes bigger after backup/restore #7627
Description
FB5 is affected. Seems like bulk inserts don't work correctly with big records. The problem is in locate_space() where the dpg_large flag is checked when the cached primary page number is used. The page is released if it has this flag, and the new record is inserted on the next empty page. As a result, each primary page has only one record. I would suggest to remove the dpg_large flag check from the locate_space(), and also from DPM_get() and DPM_next() because it prevents the cache of data page numbers to work. FB3 and FB4 don't have issues with the database size but the problem with cached page numbers is there and can be fixed the same way.