| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Streaming replication as a separate permissions |
| Date: | 2010-12-24 00:08:38 |
| Message-ID: | AANLkTik9192zA6fz4X=q8sMZGCz8P2XTz5KJJ-Yow5hk@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 23, 2010 at 5:59 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> I'm not entirely sure about this one.. I'm not against it but I'm also
>> not really 'for' it. :)
>
> 2 reasons: (a) if users need to CREATE USER, that *does* add an extra
> step and they're more likely to just choose to grant to postgres
> instead, (b) having a standard installed user (just like the user
> "postgres" is standard) would make our docs, examples and tutorials much
> easier to use.
If the user exists but is disabled by default, I'm not sure that
really provides any advantage over not having it at all. And it
certainly can't be enabled by default.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-12-24 00:11:31 | Re: Streaming replication as a separate permissions |
| Previous Message | Josh Berkus | 2010-12-23 23:29:24 | Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ |