| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dirk Heinrichs <dirk(dot)heinrichs(at)altum(dot)de> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5740: contrib/spi/moddatetime.c doesn't work with timezones. |
| Date: | 2010-11-04 20:37:12 |
| Message-ID: | 458.1288903032@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Dirk Heinrichs <dirk(dot)heinrichs(at)altum(dot)de> writes:
> Am 04.11.2010 04:55, schrieb Tom Lane:
>> I don't actually see any point in having two functions at all. Since
>> the trigger is examining the column type internally, it could perfectly
>> well do the right thing at runtime depending on column type.
> Got the point. Here's another patch, hope my limited C skills are
> sufficient... Works here, at least.
Committed with minor cleanup.
> BTW: Is there a way to achieve the same in pure PL/pgSQL or PL/perl?
plpgsql doesn't have any facility for working with run-time-determined
column names. I think it wouldn't be too hard in plperl though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Henry C. | 2010-11-05 09:54:45 | Re: BUG #5736: 9.0.1 segmentation fault (sig11) during long-lived update |
| Previous Message | Dirk Heinrichs | 2010-11-04 18:40:53 | Re: BUG #5740: contrib/spi/moddatetime.c doesn't work with timezones. |