From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Seamus Abshere <seamus(at)abshere(dot)net> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Why is pg_restore trying to create tables in pg_catalog? |
Date: | 2014-04-04 18:02:09 |
Message-ID: | 21919.1396634529@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Seamus Abshere <seamus(at)abshere(dot)net> writes:
> On 4/4/14, 12:58 PM, Tom Lane wrote:
>> Hm ... does myschema actually exist in the target database? [...] if myschema doesn't exist, the creation target devolves to pg_catalog. This is not terribly elegant but I'm not sure if there's consensus to change it.
> You're right, myschema didn't exist (I thought I had created it
> separately, etc.)
> Perhaps it would be good to warn the user (at least in --verbose) if
> it's auto-devolving to pg_catalog?
Well, the real point is we don't want it to auto-devolve to pg_catalog
in the first place. I've restarted the discussion about this on
pgsql-hackers, we'll see if it goes anywhere this time:
http://www.postgresql.org/message-id/flat/21235(dot)1396632839(at)sss(dot)pgh(dot)pa(dot)us
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-04-04 18:24:30 | Re: Indices and Foreign Tables |
Previous Message | Seamus Abshere | 2014-04-04 17:49:30 | Re: Why is pg_restore trying to create tables in pg_catalog? |