Re: pg_dump and grants to PUBLIC - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: pg_dump and grants to PUBLIC
Date
Msg-id 20060509190840.GH29652@svana.org
Whole thread Raw
In response to Re: pg_dump and grants to PUBLIC  (Blair Lowe <postgresql@zedemail.ca>)
Responses Re: pg_dump and grants to PUBLIC  (Blair Lowe <postgresql@zedemail.ca>)
List pgsql-general
On Tue, May 09, 2006 at 10:52:32AM -0600, Blair Lowe wrote:
> In my test I do not see stuff2 either. The problem here is that I have
> sensitive production data, so my tests are hard to read, and not able to
> submit here.

You don't need to show any data, just the schema will be enough. An
example you could show us would be something like below. Replace
'mydatabase' with a database and 'sometable' with a table name you know
is not is 'mydatabase' and so should not be in the dump but you say is
because it's in some other database.

$ psql mydatabase
psql version x.x.x
mydatabase> select oid from pg_class where relname = 'sometable';
  oid
-------
(0 rows)
mydatabase> \q
$ pg_dump -s mydatabase | grep 'CREATE.*sometable'
< show us the output here >

If it turns out it is in template1, you can fix this without deleting
any production data. Easiest is just login and delete stuff, though you
can recreate it using the steps in the docs.

Hope this helps,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: [PERFORM] Arguments Pro/Contra Software Raid
Next
From: Martijn van Oosterhout
Date:
Subject: Re: simple md5 authentication problems