| From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
|---|---|
| To: | Magnus Hagander <mha(at)sollentuna(dot)net> |
| Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Minor problems reloading dump in 7.0beta1 |
| Date: | 2000-02-24 15:12:04 |
| Message-ID: | Pine.GSO.4.02A.10002241608250.17421-100000@Hummer.DoCS.UU.SE |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 24 Feb 2000, Magnus Hagander wrote:
> When upgrading a server from version 6.5.2 to 7.0beta1, we hit the following
> problems when reloading the data from pg_dumpall:
>
> - Is it a "known feature" that when using "psql -f pgfull.dump" it aborts on
> the "\connect" lines from pg_dumpall?
No. It will abort if it cannot actually perform the connect, however ...
> The dump works fine if I start psql and use \i to load it. (I reliase
> the documentation says use "psql < filename", but I didn't read that
> far :-)
... makes this look like a really weird bug. What's the connect statement,
and what's the error message? (It better not abort without one. ;)
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-02-24 15:18:35 | Re: [HACKERS] Minor problems reloading dump in 7.0beta1 |
| Previous Message | Magnus Hagander | 2000-02-24 14:53:08 | Minor problems reloading dump in 7.0beta1 |