| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Radoulov, Dimitre" <cichomitiko(at)gmail(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Documentation clarification request: pg_dumpall and Large Objects |
| Date: | 2025-12-04 18:11:44 |
| Message-ID: | b8358ac2148b9daf30c27b50a8cb9c8f2c4e40f9.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, 2025-12-04 at 18:12 +0100, Radoulov, Dimitre wrote:
> Il Gio 4 Dic 2025, 16:50 Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> ha scritto:
> > On Thu, 2025-12-04 at 13:12 +0100, Radoulov, Dimitre wrote:
> > > I would like to request a clarification in the pg_dumpall
> > > documentation regarding Large Objects (LOBs). The current
> > > documentation does not explicitly state whether pg_dumpall includes
> > > Large Objects in its output.
> >
> > I admit that you have to go by circumstantial evidence here. But rather
> > than explicitly naming large objects, perhaps it would be useful to add something
> > like
> >
> > pg_dumpall is primarily intended as a tool to upgrade database clusters.
> > As such, it by default exports all data of the entire cluster.
> > The only part of the state of a database cluster that is *not* included
> > in the output of pg_dumpall are the configuration files and database parameters
> > changed with ALTER SYSTEM.
>
> Thank you again for your time and for considering the suggestion.
Attached is a patch for such a change.
I'll add it to the next commitfest.
Yours,
Laurenz Albe
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-pg_dumpall-doc-clarify-scope-and-suggested-use.patch | text/x-patch | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Radoulov, Dimitre | 2025-12-04 17:12:53 | Re: Documentation clarification request: pg_dumpall and Large Objects |