pg_dumpall behavior in 9.1beta1

From: Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com>
To: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: pg_dumpall behavior in 9.1beta1
Date: 2011-05-13 08:30:27
Message-ID: BANLkTinyMKgiuGm78oPKTX4VJENGWPRXaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dear List ,

We migrated to 9.1beta1 from 9.0.x in our development environment.
we shall report if any significant problems or issue arises out of this.

one small thing that we observed rite now regarding pg_dumpall output is that

the ALTER USER is referring to some db objects which are not created yet
and this raises an ERROR this may cause some inconvenience where restoration
is being carried out in a txn .

example of relevant sql lines is given below

CREATE ROLE pdns;
ALTER ROLE pdns WITH NOSUPERUSER INHERIT NOCREATEROLE NOCREATEDB LOGIN
NOREPLICATION PASSWORD 'md56dxxxxxxxxxxxxxxxxxxxxxxxxx' ;
ALTER ROLE pdns SET search_path TO pdns;

in above line the 'pdns' namespace does not exists yet.

regds
Rajesh Kumar Mallah.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Misa Simic 2011-05-13 09:40:01 Re: simple update query too long
Previous Message Oleg Bartunov 2011-05-13 07:46:23 Re: simple update query too long