| From: | Tim Penhey <tim(at)penhey(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paesold <mpaesold(at)gmx(dot)at>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_restore peculiarities |
| Date: | 2004-09-18 22:33:38 |
| Message-ID: | 414CB7C2.40000@penhey.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
>Without taking a position on what the Windows installer ought to do ...
>*whenever* you are restoring a pg_dump dump, you ought to do so into
>an empty database cloned from template0. If the documentation doesn't
>say that in enough places, suggest some more.
>
>
Right. If, as Tom says, that restores should be into an empty database
cloned form template0, what then is the best way to provide a data
restore facility to a user though a back end system (Tomcat & JDBC) that
will have connections open to the database that you are trying to
restore to?
Tim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paramveer.Singh | 2004-09-19 13:37:10 | order of row processing affects updates |
| Previous Message | Tom Lane | 2004-09-18 21:39:42 | Re: pg_restore peculiarities |