Re: Problems with PLPGSQL
От | Pavel Stehule |
---|---|
Тема | Re: Problems with PLPGSQL |
Дата | |
Msg-id | Pine.LNX.4.44.0311061138001.2031-100000@kix.fsv.cvut.cz обсуждение исходный текст |
Ответ на | Re: Problems with PLPGSQL (Alex <alex@meerkatsoft.com>) |
Список | pgsql-general |
Hello Don't use now or current_time, use LOCALTIMESTAMP CURRENT_TIME and CURRENT_TIMESTAMP deliver values with time zone; LOCALTIME and LOCALTIMESTAMP deliver values without time zone. Pavel On Thu, 6 Nov 2003, Alex wrote: > Hi Richard, > as for the timestamp, both ways work fine, but the other problem still > exists. using a > ''60 Min'' works just fine, but WHERE job_end + ($1::text || '' Min'' ) > > now > does not. job_end is timestamp without tz > > Alex > > Richard Huxton wrote: > > >On Thursday 06 November 2003 04:13, Alex wrote: > > > > > >>Hi, > >>I have a problem with quoting in one of my functions: > >> > >>now TIMESTAMP := ''now''; > >> > >> > > > >Your main question has been answered, but you might want now() rather than > >''now''. Off the top of my head, I think the ''now'' might get compiled as a > >value on the first run and stay at that value. > > > > > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings >
В списке pgsql-general по дате отправления: