| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kuhn, Dylan K (4520500D)" <Dylan(dot)Kuhn(at)navy(dot)mil> |
| Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: problems with pg_restore |
| Date: | 2003-07-15 16:26:29 |
| Message-ID: | 23211.1058286389@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
"Kuhn, Dylan K (4520500D)" <Dylan(dot)Kuhn(at)navy(dot)mil> writes:
> [ tries to restore a dump into a database with a different name ]
> pg_restore: [archiver (db)] could not execute query: ERROR: Database commen=
> ts may only be applied to the current database
> I'm not sure how to get around this one. Can an archived database with com=
> ments be restored to a database with a different name?
Hm. Evidently not :-(. The COMMENT ON DATABASE facility is a bit bogus
anyway (since there's no way to make the comments visible across
databases). You might be best advised not to use it.
Hackers: this seems like an extremely bad side-effect of what we thought
was a simple addition of a helpful check. I am thinking we should
either remove the check again, or downgrade it to a WARNING (though I'm
not quite sure how to phrase the warning ...). Any thoughts?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kuhn, Dylan K (4520500D) | 2003-07-15 16:54:25 | Re: problems with pg_restore |
| Previous Message | Kuhn, Dylan K (4520500D) | 2003-07-15 14:55:21 | problems with pg_restore |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-07-15 16:42:45 | Re: backend/parser compile prob |
| Previous Message | Patrick Welche | 2003-07-15 16:17:41 | Re: backend/parser compile prob |