| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Kalai R <softlinne(dot)kv(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: About Large object Storage |
| Date: | 2014-04-23 15:21:37 |
| Message-ID: | 5357DA81.1050904@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 04/23/2014 08:14 AM, Kalai R wrote:
> 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
Large objects are stored in pg_largeobject in chunks, so this is not
surprising. See below for more detail:
http://www.postgresql.org/docs/current/static/catalog-pg-largeobject.html
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kal Black | 2014-04-23 17:26:55 | WAL archiving from a standby backup strategy Postgresql 9.3 |
| Previous Message | Kalai R | 2014-04-23 15:14:46 | Re: About Large object Storage |