Devart Forums

hi,
i am using pgsqldump class to backup and restore my postgre database
using method backup and restore but when i restore large object (some what 46MB in size) i got the exception
"Exception of type 'System.OutOfMemoryException' was thrown."
while creting backup file i had made IncludeBlob = true

for backup i had write this code

Dim pgdumb As New PgSqlDump
pgdumb.Connection = Connection
pgdumb.Mode = Devart.Data.PostgreSql.DumpMode.Data
pgdumb.IncludeBlob = True
pgdumb.Backup("D:\testbackup.backup")
Connection.Close()

for restore
Dim pgDump As PgSqlDump = New PgSqlDump
pgDump.Connection = conn
pgDump.Restore("D:\testbackup.backup")
conn.close

ANY SuGESSTION PLZ HELP [/code]

We have reproduced the problem. We will investigate it and notify you about the results as soon as possible.

Thanks for your effort. I will be waiting for the update

hello shalex,
i had check this backup and restore method on two different pc (with file of size 300 mb in my database ) of same configuration (2 GB RAM,250 GB Hard Drive,os windows 7 ) ,
error remains same (out of memory) but two different size backup file created ,
on one pc error appears after 460mb backup file created and in another it appear after 14 mb backup file created , and this time error appears on backup method of pgsqldump class.

Any update from ur side on this issue

We have reproduced System.OutOfMemoryException with both Backup() and Restore() methods of the PgSqlDump class. We will investigate the problem and notify you about the results as soon as possible.

Hi,

Any update on this issue ?

We are investigating the problem.

hi shalex ,
is there any hope that this issue will get solved, my poject is getting delayed only for this issue. i hope that i get positive response from your side as soon as possible

We have implemented the PgSqlDump.BlockSize property to control the size of data block when making dump of a large object. This allows to avoid System.OutOfMemoryException because a particular "SELECT lowrite(...)" for a big "large object" will be divided into several "SELECT lowrite(...)" commands depending on the value of PgSqlDump.BlockSize. The feature will be included in the next public build of dotConnect for Postgresql (in 2-3 weeks). Is this timeframe suitable for you?

hi shalex,
This issue is important and urgent for me ,but i truly appreciate your efforts ,so i will wait for your next release, hopping that your next build get release as early as possible

New build of dotConnect for PostgreSQL 5.30.202 is available for download!
It can be downloaded from http://www.devart.com/dotconnect/postgr ... nload.html (trial version) or from Registered Users' Area (for users with valid subscription only): http://secure.devart.com/ . For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=21729 .

This build includes the PgSqlDump.BlockSize property. We recommend you to dump data directly to the file PgSqlDump.Backup(string fileName) (not to PgSqlDump.DumpText) because this can be the reason of System.OutOfMemoryException. Also set the "Default Command Timeout=0;" connection string parameter - lo_unlink can take a lot of time.

Hi shalex ,
Thanxs for you efforts we have registered version of dotConnect for PostgreSQL 4.95.152 and you provide this PgSqlDump.BlockSize property in version 5.30.202 so if we upgrade our license version ,will we able to use this property in upgraded version or not

Shilpa Mehta

The PgSqlDump.BlockSize property is available in 5.30.202 and higher versions of dotConnect for PostgreSQL. Please contact our Sales department (sales at devart*com) to check your subscription status.