| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Reducing pg_dumpall errors |
| Date: | 2012-12-04 03:37:21 |
| Message-ID: | 20121204033721.GE7675@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I recently applied the attached patch to prevent recreation of the
current database user in the dump file when in binary upgrade mode.
This was necessary because pg_upgrade will fail on any error from a
pg_dumpall restore.
It would be nice of we could do the same for non-binary-upgrade
pg_dumpall dumps, but I assume we can't because the restore might be
performed by a super user who is different from the dump user, right?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| Attachment | Content-Type | Size |
|---|---|---|
| user.diff | text/x-diff | 5.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2012-12-04 03:41:27 | Forgotten argument description in header of index_create |
| Previous Message | Noah Misch | 2012-12-04 03:34:12 | Re: ALTER TABLE ... NOREWRITE option |