Re: pg_dump DROP commands and implicit search paths

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: nconway(at)klamath(dot)dyndns(dot)org (Neil Conway)
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: pg_dump DROP commands and implicit search paths
Date: 2002-05-14 00:42:47
Message-ID: 21517.1021336967@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

nconway(at)klamath(dot)dyndns(dot)org (Neil Conway) writes:
> I'd prefer this method -- IMHO the readibility of dump scripts isn't
> a top priority (or if it is, we're not doing very well in that regard
> any). I think dump scripts should be as verbose as is necessary to
> ensure that they can't be misinterpreted.

Perhaps instead of "readability" I should have said "editability".
The thought that is lurking behind this is that you might want to
retarget a dump script to be reloaded in some other schema. If the
dump is cluttered with umpteen thousand copies of the schema name
that's going to be difficult.

Ideally I'd like the dumped object definitions to contain *no* explicit
references to their containing schema. This would allow, for example,
a pg_restore mode that loads the objects into a different schema.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2002-05-14 01:08:53 Re: pg_dump DROP commands and implicit search paths
Previous Message Tom Lane 2002-05-14 00:37:35 Re: pg_dump DROP commands and implicit search paths