| From: | Dado Feigenblatt <dado(at)wildbrain(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | backup: restoring, problems with permissions |
| Date: | 2001-11-22 01:32:32 |
| Message-ID: | 3BFC55B0.7050607@wildbrain.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I'm getting close to releasing a database for use so I changed some user
passwords,
which use to be the same for every user, including postgres.
Now I have this problem in psql:
when conected as postgres (or other user) I can only use
\c database newuser
if the newuser password is the same as the current user.
So when using psql to restore pg_dumps, psql is choking on those cases,
as it tries switching to another user before creating the tables.
Should I create everything as user postgres and change ownership later?
Is that actually possible?
Can I change pg_database.datdba and pg_class.relowner to another user id
without breaking anything?
What am I missing?
Thanks
--
Dado Feigenblatt Wild Brain, Inc.
Technical Director (415) 216-2053
dado(at)wildbrain(dot)com San Francisco, CA.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-22 01:40:46 | Re: TOAST performance (was Re: [GENERAL] Delete Performance) |
| Previous Message | Dado Feigenblatt | 2001-11-22 01:32:06 | backup: pg_dumpall and full backups in general |