From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: Herb Blacker <hhb@isgenesis.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: [NOVICE] Loading current_user and current_timestamp using COPY
Date: Thu, 11 Oct 2001 01:11:06 -0400
Message-ID: <9479.1002777066@sss.pgh.pa.us> (raw)
In-Reply-To: <web-145846@davinci.ethosmedia.com>
References: <web-145846@davinci.ethosmedia.com>
>> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, hhb@isgenesis.com
Subject: Re: [NOVICE] Loading current_user and current_timestamp using COPY
In-Reply-To: <9479.1002777066@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox