Re: [NOVICE] Loading current_user and current_timestamp using COPY

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Josh Berkus" <josh(at)agliodbs(dot)com>
Cc: "Herb Blacker" <hhb(at)isgenesis(dot)com>, pgsql-sql(at)postgresql(dot)org
Subject: Re: [NOVICE] Loading current_user and current_timestamp using COPY
Date: 2001-10-11 05:11:06
Message-ID: 9479.1002777066@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

>> 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

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Alexander Deruwe 2001-10-11 10:48:02 BIGINT's and indexes.
Previous Message Josh Berkus 2001-10-11 04:20:12 Re: [NOVICE] Loading current_user and current_timestamp using COPY