From: | Kalai R <softlinne(dot)kv(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: About Large object Storage |
Date: | 2014-04-23 15:14:46 |
Message-ID: | CAGxuanPO8pwEPgnVOcBXr-xm7cXZFyS0jCDHRTqtKi=nXK=9Qw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Kalai R <softlinne(dot)kv(at)gmail(dot)com> 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2014-04-23 15:21:37 | Re: About Large object Storage |
Previous Message | Tom Lane | 2014-04-23 14:07:33 | Re: [GENERAL] aggregate returning anyarray and 'cannot determine result data type' |