| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: A fixed user id for the postgres user? |
| Date: | 2001-09-07 22:19:18 |
| Message-ID: | Pine.LNX.4.30.0109072158120.680-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane writes:
> I've been thinking a little bit about how one might recover from Really
> Stupid Mistakes, like deleting one's only superuser pg_shadow entry.
> What I'm thinking is that if we hard-wired usesysid = 1 for the
> superuser, it'd be possible to arrange for standalone backends to fire
> up with that sysid and superuserness assumed, and not consult pg_shadow
> at all. Then you'd have a platform in which you could do CREATE USER.
FYI: I'm working on this now. It seems to work out nicely; at least I
was able to recover from DELETE FROM pg_shadow; without a problem.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D'Arcy J.M. Cain | 2001-09-07 22:33:19 | Re: CVS access |
| Previous Message | Bruce Momjian | 2001-09-07 22:02:32 | Re: Escaping strings for inclusion into SQL queries |