| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Why pg_hba not in table? |
| Date: | 2006-02-07 21:39:22 |
| Message-ID: | 1139348361.22740.100.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2006-02-07 at 15:37, Michael Fuhr wrote:
> On Tue, Feb 07, 2006 at 03:24:01PM -0500, Tom Lane wrote:
> > One other small point is the bootstrapping problem: if you can't get
> > into the database to modify the config table, you've got trouble.
>
> Hence MySQL's --skip-grant-tables option; if you've locked yourself
> out then you have to disable security entirely to get back in and
> fix the problem. With a configuration that you can edit from outside
> the database, you can usually get back in without having to punch
> as big a hole.
And you can change pg_hba.conf on the fly, so you don't have to restart
a 24/7 database because you locked the superuser out.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-07 21:55:55 | Re: Why pg_hba not in table? |
| Previous Message | Michael Fuhr | 2006-02-07 21:37:42 | Re: Why pg_hba not in table? |