Re: Forcing pg_dump NOT to use "INSERT..."
От
Stef
Тема
Re: Forcing pg_dump NOT to use "INSERT..."
Дата
Msg-id
20031105142300.5c1b25d2.svb@ucs.co.za
Список
Дерево обсуждения
Forcing pg_dump NOT to use "INSERT..." "David F. Skoll" <dfs@roaringpenguin.com>
Re: Forcing pg_dump NOT to use "INSERT..." Tom Lane <tgl@sss.pgh.pa.us>
Re: Forcing pg_dump NOT to use "INSERT..." "Jaskier" <jaskierbard@poczta.onet.pl>
Microsoft access verses postgresql Geoffrey <esoteric@3times25.net>
Re: Microsoft access verses postgresql Michelle Murrain <tech@murrain.net>
Re: Microsoft access verses postgresql Geoffrey <esoteric@3times25.net>
Re: Microsoft access verses postgresql Michelle Murrain <tech@murrain.net>
Re: Microsoft access verses postgresql Geoffrey <esoteric@3times25.net>
Re: Microsoft access verses postgresql Kaarel <kaarel@future.ee>
Re: Microsoft access verses postgresql Geoffrey <esoteric@3times25.net>
Re: Microsoft access verses postgresql William Yu <wyu@talisys.com>
Re: Microsoft access verses postgresql "David Green" <david@sagerobot.com>
=> This is extremely hard to believe. I can see no way that pg_dump will => do that unless you explicitly ask for it (-d or -D switch, or one of the => long variants of same). I know of a lot of people that confuses the -d switch as an option indicating the database name to follow. It is also usually very hard to convince people that they dumped INSERT statements in stead of COPY once you sit with a restore that takes a little longer than usual...
В списке pgsql-admin по дате отправления
