Received: from bubbles.electricutopia.net (bubbles.electricutopia.net [63.214.178.76]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3CJPA864089 for ; Thu, 12 Apr 2001 15:25:10 -0400 (EDT) (envelope-from dave@slickness.org) Received: from localhost (dave@localhost) by bubbles.electricutopia.net (8.9.3/8.9.3) with ESMTP id MAA13857; Thu, 12 Apr 2001 12:18:36 -0700 Date: Thu, 12 Apr 2001 12:18:36 -0700 (PDT) From: David Olbersen X-X-Sender: To: Peter Eisentraut cc: Subject: Re: DROP TABLE in transaction In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200104/186 X-Sequence-Number: 2536 On Thu, 12 Apr 2001, Peter Eisentraut wrote: > Because DROP TABLE removes the table file on disk, and you can't roll back > that. Actually, in 7.1 you can. ;-) Well I understand that it's being taken from the disk, but why does that action have to be done *right now*? Why can't it be postponed until I type 'commit;' ? I wonder how much time this addition would have saved those of us who type quickly and use the tab-completion too much :) -- Dave