Re: calling elog possibly causing problem in DirectFunctionCall1

From: "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: calling elog possibly causing problem in DirectFunctionCall1
Date: 2006-12-01 17:59:45
Message-ID: a97c77030612010959i7f864f5cgb551e6ced61bab3a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On 12/1/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com> writes:
> > data->time_stamp =
> > DirectFunctionCall1(timestamptz_in, CStringGetDatum("now"));
>
> This code is incorrect, as timestamptz_in takes three arguments.

Dear Sir,

thanks for the kind reply.

field time_stamp of data is declared as:
Datum time_stamp;

it is supposed to be populated with current timestamp , (now())
can you please tell me what should be passed as the third argument?

Regds
Mallah.

regards, tom lane
>

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Rajesh Kumar Mallah 2006-12-01 18:58:02 Re: calling elog possibly causing problem in DirectFunctionCall1
Previous Message Tom Lane 2006-12-01 17:47:43 Re: calling elog possibly causing problem in DirectFunctionCall1