Design question: Should "postgres" own all the db objects?

From: Andreas <maps(dot)on(at)gmx(dot)net>
To: PostgreSQL <pgsql-general(at)postgresql(dot)org>
Subject: Design question: Should "postgres" own all the db objects?
Date: 2009-07-13 01:10:49
Message-ID: 4A5A8999.40203@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

who should own the db objects?
I once read one should not let postgres or any other superuser own the
tables and what not.
Instead one should better create a separate user role with little
privileges to be the owner.
I'm not quite sure why this was abvised. Maybe like not using root for
everyday work.

What is commonly regarded as good design in this issue?

Thanks for your input

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andreas 2009-07-13 02:41:48 How move a referenced table between schemas?
Previous Message Alvaro Herrera 2009-07-13 01:04:56 Re: how drop a role that owns stuff ?