From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Masaru Sugawara <rk73(at)echna(dot)ne(dot)jp> |
Cc: | herve(at)elma(dot)fr, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Trouble with pg_dumpall import with 7.2 |
Date: | 2002-02-20 19:06:46 |
Message-ID: | 1811.1014232006@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Masaru Sugawara <rk73(at)echna(dot)ne(dot)jp> writes:
> (1)create function mydate(timestamp) returns date as '
> select date($1);
> ' language 'sql' with (iscachable);
If you do it that way then you are simply opening yourself up to exactly
the error that the noncachability check is trying to save you from
making.
You could probably do it safely by hard-wiring the time zone to be used
into the function. I think something like this would work:
create function mydate(timestamp with time zone) returns date as '
select date($1 AT TIME ZONE ''EST'');
' language 'sql' with (iscachable);
(substitute time zone of your choice, of course).
BTW, if the table is at all large then you'd probably be better off to
use a plpgsql function instead. SQL-language functions are rather
inefficient IIRC.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2002-02-20 23:15:53 | Re: Foreign Key work for 7.3+ |
Previous Message | Tom Lane | 2002-02-20 18:53:19 | Re: pg_type defaults |