| From: | Sékine Coulibaly <scoulibaly(at)gmail(dot)com> |
|---|---|
| To: | Kouadio denis KOFFI <etskkd(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Fwd: request |
| Date: | 2015-11-20 15:57:50 |
| Message-ID: | CAD8n-For8pqHt6g+_A4svUORv4tKFW_P5dYaArB78Ha_hSwT5A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Kouadio,
How did you instanciate pg_dump ? As per the documentation, the large
objects might not be dumped, see :
-b
--blobs
Include large objects in the dump. This is the default behavior except when
--schema, --table, or --schema-only is specified, so the -b switch is only
useful to add large objects to selective dumps.
cheers
2015-11-19 17:27 GMT+01:00 Kouadio denis KOFFI <etskkd(at)gmail(dot)com>:
> hello, I'm KOFFI Denis from COTE D'IVOIRE, i use postgresql 9.1 since
> 2012. i have a problem today. i make a backup and i restored it on another
> computer, all go well but when i want to read large objects with jdbc it
> returns error like large object "100140" does not exist.
> thank you to help me.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-11-20 17:01:28 | Re: [BUGS] BUG #13779: Inherited check constraint becomes non-inherited when related column is changed |
| Previous Message | Guillaume Lelarge | 2015-11-20 12:37:45 | Re: Confusing error message with too-large file in pg_basebackup |