| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | "sivapostgres(at)yahoo(dot)com" <sivapostgres(at)yahoo(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Pgsql-general <pgsql-general(at)postgresql(dot)org>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Subject: | Re: To take backup of Postgresql Database without large objects |
| Date: | 2025-04-12 05:37:19 |
| Message-ID: | 92A90844-8669-477C-90E9-41D619814D8C@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Apr 11, 2025, at 22:34, sivapostgres(at)yahoo(dot)com wrote:
> Then I've misunderstood large objects. Is there document to explain large objects?
Large objects are a relatively old and now little-used feature of PostgreSQL that predates the bytea type:
https://www.postgresql.org/docs/current/largeobjects.html
As was mentioned, you cannot exclude individual columns with pg_dump; you have to exclude the entire table.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-04-12 06:00:37 | Re: To take backup of Postgresql Database without large objects |
| Previous Message | sivapostgres@yahoo.com | 2025-04-12 05:34:52 | Re: To take backup of Postgresql Database without large objects |