Re: pg_dump, --exclude-table-data - Mailing list pgsql-docs

From Laurenz Albe
Subject Re: pg_dump, --exclude-table-data
Date
Msg-id 5a24b53cff1c4a723e21e4ef980d5bdcb74f33d1.camel@cybertec.at
Whole thread Raw
In response to pg_dump, --exclude-table-data  (PG Doc comments form <noreply@postgresql.org>)
List pgsql-docs
On Sat, 2020-02-01 at 08:33 +0000, PG Doc comments form wrote:
> I cannot find and understand what happens, if I will ommit the table data
> for a table where primary keys are refenced by foreignkeys from other
> tables. I think the integrity will break and such backup/dump is
> unusable...? Or is there a way how to handle this during restore?
> 
> (What I want to do is anonymize the content. I don't want to give user data
> (User table), but lot of foreignkeys reference them. Something like
> exporting all the rows with only primary key and foreign keys (which meet my
> needs if just int/bigint are used for keys) + random content in other
> fields. I understand that this is difficult to achieve and the completely
> omiitted data will be ok - if there is not integrity problem during
> restore.)

Yes, if you omit the data for a table, restoring a foreign key that relies
on the data will fail.  Note that only the foreign key will fail and not
get created, but the tables themselves will be restored.

Yours,
Laurenz Albe




pgsql-docs by date:

Previous
From: PG Doc comments form
Date:
Subject: Users/Roles do not align.
Next
From: PG Doc comments form
Date:
Subject: Move description of general lock behaviour out of the "13.3.1. Table-level Locks section"