| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Brook Milligan <brook(at)biology(dot)nmsu(dot)edu>, peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] psql -f inconsistency with "copy from stdin" |
| Date: | 2000-01-12 16:19:59 |
| Message-ID: | Pine.BSF.4.21.0001121218080.46499-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 12 Jan 2000, Tom Lane wrote:
> > pg_dump would have to be changed to correspond.
>
> IMHO any proposal that requires changing pg_dump is a non-starter,
> because it will fail when people try to load 6.5 or earlier dumps
> into 7.0. But fortunately, pg_dump doesn't use \copy ...
I'm confused here...why would "any proposal that requires changing pg_dump
is a non-starter"? How does changing pg_dump in v7.0 affect pg_dump in
v6.5?
As long as I can reload my v6.5 data into a v7.0 database using the
pg_dump from v6.5, confused as to why v7.0s pg_dump matters...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cory Kempf | 2000-01-12 16:23:35 | Re: postgresql installation |
| Previous Message | Tom Lane | 2000-01-12 16:09:11 | Re: [HACKERS] FETCH without FROM/IN |