Re: date_in function

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dragos Manzateanu <dragon(at)mail(dot)dntis(dot)ro>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: date_in function
Date: 2002-04-17 15:19:12
Message-ID: 6625.1019056752@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dragos Manzateanu <dragon(at)mail(dot)dntis(dot)ro> writes:
> na = SPI_fnumber(trigdata->tg_relation->rd_att, "my_date");
> memset(select, 0, sizeof(select));
> sprintf(select, "1/1/2002");
> newval = DirectFunctionCall1(date_in, CStringGetDatum(select));
> rettuple = SPI_modifytuple(trigdata->tg_relation, rettuple, 1, &na, &newval,
> NULL);
> if(rettuple == NULL) elog(ERROR, "my_function: %d returned by
> SPI_modifytuple", SPI_result);

> when i test that my server goes down. What I missed ?

I doubt that the problem is with date_in. Have you tried backtracing
in the core dump?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mlw 2002-04-17 15:22:37 Re: Index Scans become Seq Scans after VACUUM ANALYSE
Previous Message Tom Lane 2002-04-17 15:16:16 Re: Index Scans become Seq Scans after VACUUM ANALYSE