Added to TODO:
* Set proper permissions on non-system schemas during db creation
Currently all schemas are owned by the super-user because they are
copied from the template1 database.
I have added the v2 version of this patch to the patch queue (attached).
I do apologize for not having looked at this patch sooner, but it's been
at the bottom of the priority queue :-(
No need to apoligize.
In general I do not like the approach of using SPI for this. [...]
Ok.
Well, my
Is there a TODO here?
---
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Fabien COELHO wrote:
Please find attached a preliminary patch to fix schema ownership on first
connection. It is for comments and
Bruce Momjian [EMAIL PROTECTED] writes:
Fabien COELHO wrote:
Please find attached a preliminary patch to fix schema ownership on first
connection. It is for comments and advices as I still have doubts about
various how-and-where issues, thus it is not submitted to the patch list.
I have
I'm also wondering about what side-effects this will have on pg_dump
behavior. In particular, will pg_dump try to ALTER OWNER public,
and if so will that be appropriate? We haven't previously needed to
assume that we are restoring into a database with the same datowner as
we dumped from...
In my
