Re: dump + restore didn't include schemas

From: "Dan Langille" <dan(at)langille(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: dump + restore didn't include schemas
Date: 2004-01-31 17:01:13
Message-ID: 401B9909.3871.1AA8C384@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 31 Jan 2004 at 11:56, Tom Lane wrote:

> "Dan Langille" <dan(at)langille(dot)org> writes:
> >>> I upgraded two servers today from 7.3.* to 7.4.1. In both cases, the
> >>> schemas which existed in the original databases were not created in
> >>> the new database.
>
> > I found three of these messages in /var/log/messages on the box which
> > had the problem.
>
> > ERROR: permission denied for database pg_freebsddiary.org.schemas
>
> Oh, I bet I know what this is: the owners of those schemas don't have
> CREATE SCHEMA privileges, right? You made the schemas as superuser with
> CREATE SCHEMA foo AUTHORIZATION bar.
>
> 7.4's pg_dump will use AUTHORIZATION so that situations like this
> restore correctly, but 7.3's pg_dump is stupid and tries to create the
> schema as its owner.

Does it matter that I used pg_dumpall?

> In general I recommend that during an upgrade, you use the new version's
> pg_dump to dump from the old server. This way you get the benefit of
> whatever improvements have been made in pg_dump since the previous
> release.

Should that recommendation be added to the "If You Are Upgrading"
section of INSTALL?
--
Dan Langille : http://www.langille.org/
BSDCan - http://www.bsdcan.org/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-01-31 17:11:03 Re: dump + restore didn't include schemas
Previous Message Tom Lane 2004-01-31 16:56:00 Re: dump + restore didn't include schemas