Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9B5BIn47369 for ; Thu, 11 Oct 2001 01:11:18 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f9B5B6I09482; Thu, 11 Oct 2001 01:11:06 -0400 (EDT) To: "Josh Berkus" cc: "Herb Blacker" , pgsql-sql@postgresql.org Subject: Re: [NOVICE] Loading current_user and current_timestamp using COPY In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Wed, 10 Oct 2001 21:20:12 -0700" Date: Thu, 11 Oct 2001 01:11:06 -0400 Message-ID: <9479.1002777066@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200110/145 X-Sequence-Number: 5100 >> Although...if COPY can handle the now() function, it should be able >> to handle the current_user/current_timestamp without too much overhead. Eh? COPY most assuredly does not handle the now() function, nor any other function call. It will accept 'now' --- no parens --- as an input for datetime datatypes, but that's because those datatypes do, not because COPY is doing anything special. IMHO the entire point of COPY is to load bulk data as quickly as possible ... if you want any convenience processing done for you, you should be using INSERT not COPY. regards, tom lane