Re: Issue with COPY command - Mailing list pgsql-general

From David G Johnston
Subject Re: Issue with COPY command
Date
Msg-id 1409147579827-5816553.post@n5.nabble.com
Whole thread Raw
List pgsql-general
swaroop wrote
> In need of some help - The use case is to insert current time in UTC for a
> timestamp column
> using COPY command . It works fine if i just have now() in csv file input.
> But if i add
> now() at time zone 'utc'  it gives the error as
> ERROR:  invalid input syntax for type timestamp: "now() at time zone
> 'utc'"
>
> I need to enforce UTC somehow to current time. Any pointers here pls ?

Your timestamp column target should be with timezone and, if so, whatever
value 'now' resolves to will be converted to and stored in UTC
automatically.

Though typically you are better advised to simply not import a default
column and instead leave the table default expression to assign a value.

Also, you cannot use functions when importing via copy.  The 'now' in this
case is a special keyword interpreted by the timestamp input function and is
not actually a (direct) reference to the now() function provided by
PostgreSQL.

David J.





--
View this message in context: http://postgresql.1045698.n5.nabble.com/Issue-with-COPY-command-tp5816527p5816553.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


pgsql-general by date:

Previous
From: Piotr Gasidło
Date:
Subject: Re: SELECT 'NOW()' - OK, SELECT 'CLOCK_TIMESTAMP()' - ERROR
Next
From: Gabriele Lohss
Date:
Subject: Re: pgbouncer setup in the architecture