## Answer It's possible that memory shortage occurred due to large files being attached to records and these attachments being stored within the PostgreSQL database. If the number of attached large files is not extensive, it may be possible to execute pg_dump by individually downloading and backing up the attached files, then removing the attachments from the database. --- ## Overview Please confirm the prerequisites before implementing the operational procedures. ## Prerequisites 1. The following is a workaround for when the number of large attached files is not extensive and the Provider value in the configuration file "[BinaryStorage.json](/en/manual/binary-storage-json)" is "Rds". 1. When the Provider value is "Rds", attached files are stored in the Binaries table and Binaries_deleted table within PostgreSQL. 1. Attached files in the Binaries table can be deleted through Pleasanter's screen operations. 1. The Binaries_deleted table stores deleted attached files (for the purpose of restoration and reference from history). 1. Attached files are BASE64 encoded and stored as strings within the database. 1. The guideline for large files is 1GB in file size after encoding. 1. BASE64 encoding increases file size by approximately 30%. ## Operational Procedures 1. Identify target files and target records by checking file sizes in the Size column of the database's Binaries table. 1. Open the edit screen for the target record in Pleasanter, individually download large attached files, and verify and save them. 1. Delete the attached files in Pleasanter. 1. The Binaries_deleted table also has a Size column with the same layout as the Binaries table. Identify records with large Size column values and delete them with DELETE queries. 1. Execute the pg_dump command to migrate the database. 1. After database migration, individually upload the downloaded files to the target records. ## Related Information <div id="ManualList"><ul><li><a href="/en/manual/binary-storage-json">Set Parameter: BinaryStorage.json</a><span>10.24.2025 up</span></li></ul></article></div><input id="SearchTextHidden" type="hidden" value="" />