Re: Docs pg_restore: Shouldn't there be a note about -n ?

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Florents Tselai <florents(dot)tselai(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Docs pg_restore: Shouldn't there be a note about -n ?
Date: 2026-02-03 18:37:34
Message-ID: 202602031834.gdtouimq464x@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-Jan-05, Florents Tselai wrote:

> I consolidated the dependency warnings into the main "Notes" section for
> both pg_dump and pg_restore, removing the repetitive per-switch notes.
>
> For the -e switch in pg_dump, I replaced the removed dependency note
> with a specific warning that extension installation files (shared libs,
> control files) are not included.
> I agree that maintaining a specific note for -e is the right move.
> Given the broad usage of pg_dump, it is helpful to be explicit that the
> dump only captures the SQL definitions and not the underlying system
> binaries.

Makes sense. I have pushed this.

I just noticed though, that the issue in pg_restore applies not only to
the -n and -t switches, but also to -L (where you specify a file with a
list of objects to restore) and --filter. Maybe we can this new
paragraph mention that as well.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"No renuncies a nada. No te aferres a nada."

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2026-02-03 19:04:31 Re: GSoC 2026: Call for Mentors, Project Ideas and Project Idea Reviews
Previous Message Jim Jones 2026-02-03 18:22:16 Re: Additional message in pg_terminate_backend