Re: request clarification on pg_restore documentation

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: jcarson(at)fastmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: request clarification on pg_restore documentation
Date: 2022-10-06 14:28:27
Message-ID: Yz7mC08uk9Y7N1jA@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers


Thread moved to hackers.

---------------------------------------------------------------------------

On Thu, Sep 29, 2022 at 02:30:13PM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/app-pgrestore.html
> Description:
>
> pg_restore seems to have two ways to restore data:
>
> --section=data
>
> or
>
> --data-only
>
> There is this cryptic warning that --data-only is "similar to but for
> historical reasons different from" --section=data
>
> But there is no further explanation of what those differences are or what
> might be missed or different in your restore if you pick one option or the
> other. Maybe one or the other option is the "preferred current way" and one
> is the "historical way" or they are aimed at different types of use cases,
> but that's not clear.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Indecision is a decision. Inaction is an action. Mark Batterson

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2022-10-06 23:50:26 Comparison Predicates - example - documentation seems contradictory?
Previous Message Bruce Momjian 2022-10-06 14:28:15 Re: request clarification on pg_restore documentation

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-10-06 15:19:38 Re: Transparent column encryption
Previous Message Bruce Momjian 2022-10-06 14:28:15 Re: request clarification on pg_restore documentation