Re: [HACKERS] psql -f inconsistency with "copy from stdin"
| От | The Hermit Hacker |
|---|---|
| Тема | Re: [HACKERS] psql -f inconsistency with "copy from stdin" |
| Дата | |
| Msg-id | Pine.BSF.4.21.0001121218080.46499-100000@thelab.hub.org обсуждение исходный текст |
| Ответ на | Re: [HACKERS] psql -f inconsistency with "copy from stdin" (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [HACKERS] psql -f inconsistency with "copy from stdin"
|
| Список | 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@hub.org secondary: scrappy@{freebsd|postgresql}.org
В списке pgsql-hackers по дате отправления: