| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | jcarson(at)fastmail(dot)com |
| Subject: | request clarification on pg_restore documentation |
| Date: | 2022-09-29 14:30:13 |
| Message-ID: | 166446181317.661.16517798061228916974@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ekaterina Kiryanova | 2022-09-30 15:10:01 | Documentation fixes |
| Previous Message | Laurenz Albe | 2022-09-28 17:47:43 | Re: suggest about bpchar data type in the document |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Coutu | 2022-09-29 14:32:58 | Re: disfavoring unparameterized nested loops |
| Previous Message | Ronan Dunklau | 2022-09-29 14:15:25 | Re: A potential memory leak on Merge Join when Sort node is not below Materialize node |