| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, George Neuner <gneuner2(at)comcast(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Freezing localtimestamp and other time function on some value |
| Date: | 2016-04-12 18:05:02 |
| Message-ID: | 10572.1460484302@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juan Carlos Michaca Lucero | 2016-04-12 18:37:17 | Re: Table seems empty but its size is in gigabytes |
| Previous Message | Tom Lane | 2016-04-12 17:50:06 | Re: Freezing localtimestamp and other time function on some value |