Re: Odd warning from pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Odd warning from pg_dump
Date: 2016-03-08 16:06:47
Message-ID: 10757.1457453207@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> I think the real question is if "-n '*'" should still exclude
> 'pg_catalog'. Fixing the issue with defined pseudo types is wonderful,
> but aren't you going to end up with a dump you can't restore,
> regardless?

Yeah, perhaps so. The thread on -general has also produced the
information that pg_dump -t '*' tries to dump system catalogs as if
they were user tables, which is another pretty useless bit of behavior.
So maybe we should drop the hunk you've got there (which frankly seems a
bit of a kluge) and instead hot-wire things so that stuff in pg_catalog
is excluded even if it would otherwise match the inclusion lists.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2016-03-08 16:07:18 Re: VS 2015 support in src/tools/msvc
Previous Message Melvin Davidson 2016-03-08 16:04:15 Re: Exclude pg_largeobject form pg_dump