Re: Restore dump into different databases/owners

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andreas Haumer <andreas@xxxxxxxxx> writes:
> Tom Lane schrieb:
>> Exactly what problems did you have using "-O -U user" ?

> So, the main problem is the call to
> CREATE PROCEDURAL LANGUAGE plpgsql;
> on the "mwdb" schema which contains all the tables, functions etc.

Right.  As of 8.3, the default permissions arrangement will allow
database owners to create trusted procedural languages for themselves,
so this dump would work for a non-superuser (though you'd still have
to ignore the error from attempting to comment SCHEMA public --- I
suppose we ought to look into keeping pg_dump from emitting that
comment).

Otherwise, the recommended procedure is for the superuser to load
any required procedural languages when he makes the empty database.
The database owner can take it from there.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux