Re: Freezing localtimestamp and other time function on some value - Mailing list pgsql-general

From David G. Johnston
Subject Re: Freezing localtimestamp and other time function on some value
Date
Msg-id CAKFQuwZv0FzN68PR9nZ_xyoV-sdhYXzqnTkgv7jUd5KWrwbdyA@mail.gmail.com
Whole thread Raw
In response to Re: Freezing localtimestamp and other time function on some value  (Alex Ignatov <a.ignatov@postgrespro.ru>)
List pgsql-general
On Wed, Apr 13, 2016 at 10:14 AM, Alex Ignatov <a.ignatov@postgrespro.ru> wrote:
Some quick and dirty issue resolution is simple:
set search_path = my_time_schema on db layer. After that you dont need to change any code. And can take for example freeze.fixed_date from config =)
where my_time_schema contains all time function than I want to freeze.
Nevertheless i dont know how to deal with say localtimestamp with this approach %). Where localtimestamp is defined? pg_catalog doesnt have it

Some thoughts about localtimestamp redifinition with search_path?

​"localtimestamp" isn't really a function but a keyword​
 
​that somewhat behaves as one.


​Specifically those defined in 9.9.4​

The fact that they can be used without adding the parenthesis is a big give-away.  All true functions must use them.  Note that these time function do allow parentheses but they have a different meaning - to specify precision as opposed to passing arguments - though the do look similar.

​David J.​

pgsql-general by date:

Previous
From: Alex Ignatov
Date:
Subject: Re: Freezing localtimestamp and other time function on some value
Next
From: Daniel Lenski
Date:
Subject: sign function with INTERVAL?