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

From Alex Ignatov
Subject Re: Freezing localtimestamp and other time function on some value
Date
Msg-id 570E2AAF.4060209@postgrespro.ru
Whole thread Raw
In response to Re: Freezing localtimestamp and other time function on some value  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

On 12.04.2016 21:05, Tom Lane wrote:
> I wrote:
>> 3. While I can see the point of wanting to, say, test weekend behavior
>> on a weekday, I do not see how a value of now() that doesn't advance
>> between transactions would represent a realistic test environment for
>> an app with time-dependent behavior.
> BTW, one possible way of meeting that particular requirement is to fool
> with your timezone setting.
>
> regression=# select timeofday();
>                timeofday
> -------------------------------------
>   Tue Apr 12 14:01:53.254286 2016 EDT
> (1 row)
>
> regression=# set time zone interval '+120 hours';
> SET
> regression=# select timeofday();
>                timeofday
> --------------------------------------
>   Sun Apr 17 18:01:58.293623 2016 +120
> (1 row)
>
>             regards, tom lane
>
>
Oh!
This is better than nothing =)!

--
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



pgsql-general by date:

Previous
From: Alex Ignatov
Date:
Subject: Re: Freezing localtimestamp and other time function on some value
Next
From: Christoph Moench-Tegeder
Date:
Subject: Re: Returning values from an array of JSONB objects.