| From: | Thomas Swan <tswan(at)idigx(dot)com> |
|---|---|
| To: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: inconsistent owners in newly created databases? |
| Date: | 2004-05-03 16:46:48 |
| Message-ID: | 40967778.2060507@idigx.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>Thomas Swan <tswan(at)idigx(dot)com> writes:
>
>
>>Fabien COELHO wrote:
>>
>>
>>>You don't want to update ownership of tables in system schemas.
>>>
>>>
>>>
>>AFAICS, any changes they make are localized to their database not the
>>whole database system.
>>
>>
>
>A database owner who is not a superuser should *not* be able to fool with
>the built-in catalog entries.
>
>Database owner != superuser, and I don't want us blurring the distinction...
>
>
>
With regards to changing ownership, is there a way to determine what is
a "built-in" catalog entry? If the database that was the template was
modified, can the createdb routine determine what is core and what was
added?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2004-05-03 16:50:48 | Re: inconsistent owners in newly created databases? |
| Previous Message | Tom Lane | 2004-05-03 16:37:20 | Re: Weird prepared stmt behavior |