From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ROLE VALID UNTIL timezone? |
Date: | 2019-11-28 03:25:14 |
Message-ID: | ba37c697-bf91-9cd6-d461-9079dab35daf@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/27/19 2:25 PM, Adrian Klaver wrote:
> On 11/27/19 2:19 PM, Ron wrote:
>> Hi,
>>
>> In 9.6, does it default to UTC, the postgresql.conf timezone value
>> (US/Eastern) value or to local system time?
>>
>>
>
> test_(postgres)# show timezone;
> TimeZone
> ------------
> US/Pacific
>
> test_(postgres)# create role ts_test valid until '12/31/2020';
> CREATE ROLE
>
> ts_test | Cannot login +| {}
> | Password valid until 2020-12-31 00:00:00-08 |
>
> Best guess it operates like if specifying a value for a timestamptz field.
Decided to see if guess was correct:
Line 94
Datum validUntil_datum; /* same, as timestamptz Datum */
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2019-11-28 03:45:54 | Re: jsonb_set() strictness considered harmful to data |
Previous Message | Michael Paquier | 2019-11-28 02:35:29 | Re: jsonb_set() strictness considered harmful to data |