Received: from mail.interchange.ca (ns.interchange.ca [216.126.79.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e72LgTG06140 for ; Wed, 2 Aug 2000 17:42:29 -0400 (EDT) Received: by mail.interchange.ca (Fastmailer, from userid 555) id EEA789CAB; Wed, 2 Aug 2000 17:42:13 -0400 (EDT) MIME-Version: 1.0 Message-Id: <398895B5.000093.16285@frodo.searchcanada.ca> Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_DMPOU1966ERNTT4D7TH0" To: jlapham@gandalf.bioqmed.ufrj.br Subject: Re: on line numbers, drop table errors, and log files Cc: pgsql-sql@postgresql.org From: "Michael Richards" X-Fastmail-IP: 24.42.110.18 Date: Wed, 2 Aug 2000 17:42:13 -0400 (EDT) X-Archive-Number: 200008/14 --------------Boundary-00=_DMPOU1966ERNTT4D7TH0 Content-Type: Text/Plain Content-Transfer-Encoding: 7bit > As I mentioned earlier, your solution worked great. I am a bit > puzzled about the syntax that is created by my old method, using > "pg_dump -D -u -a". I wonder why it creates "create sequence ..." > commands instead of "update sequence ..."? That is a good question. I do not know the answer. Since it is understood that you are dumping the data and not the schema, that would imply to me that the schema (sequences included) should already exist and need to be updated. Of course I feel that implicitly it should be cleaning out the contents of the tables when this is done as well. Perhaps someone on the team could comment on this. -Michael _________________________________________________________________ http://fastmail.ca/ - Fast Free Web Email for Canadians --------------Boundary-00=_DMPOU1966ERNTT4D7TH0--