| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Surafel Temesgen <surafel3000(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: possibility to read dumped table's name from file |
| Date: | 2021-10-04 12:54:27 |
| Message-ID: | 4EC0D9B1-2BE9-4226-9D80-9070DF72E620@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 2 Oct 2021, at 08:18, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
> So the issue is not as serious as it seemed.
This is also not related to this patch in any way, or am I missing a point
here? This can just as well be achieved without this patch.
> The complaint remaining is only that this could somehow be documented better.
The pg_dump documentation today have a large highlighted note about this:
"When --include-foreign-data is specified, pg_dump does not check that the
foreign table is writable. Therefore, there is no guarantee that the
results of a foreign table dump can be successfully restored."
This was extensively discussed [0] when this went in, is there additional
documentation you'd like to see for this?
--
Daniel Gustafsson https://vmware.com/
[0] https://postgr.es/m/LEJPR01MB0185483C0079D2F651B16231E7FC0@LEJPR01MB0185.DEUPRD01.PROD.OUTLOOK.DE
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-10-04 12:56:21 | Re: 2021-09 Commitfest |
| Previous Message | kuroda.hayato@fujitsu.com | 2021-10-04 12:53:49 | RE: Allow escape in application_name |