Search Postgresql Archives

Re: About Large object Storage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have used custom format archieve in pg_dump. 

I have used the following command in plpgsql function to insert the image.
lo_import(xlogopath)

After I inserted one image more records are created in pg_largeobject and pg_largeobject_metadata tables other than the OID returned from lo_import


On Wed, Apr 23, 2014 at 7:11 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Kalai R <softlinne.kv@xxxxxxxxx> writes:
> I am using postgresql 9.3 in Windows. I take data backup using pg_dump. The
> backup file size is 5 MB only. After that I insert 8 images using large
> object.

> The total size of 8 images are 24 MB. After insert large object only, I
> take data backup using pg_dump. Now the backup file size becomes 246 MB.

The size of the output file will be about twice the length of the large
object(s), since plain-text pg_dump format prints the large object
contents in hex.  I'd take a second look at exactly how you inserted
the large objects; it seems highly likely that you inserted them multiple
times or bloated their contents somehow.

                        regards, tom lane


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux