| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kalai R <softlinne(dot)kv(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: About Large object Storage |
| Date: | 2014-04-23 13:41:26 |
| Message-ID: | 21373.1398260486@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | Tom Lane | 2014-04-23 14:07:33 | Re: [GENERAL] aggregate returning anyarray and 'cannot determine result data type' |
| Previous Message | Rémi Cura | 2014-04-23 13:39:44 | Re: About Large object Storage |