From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | mjfshark(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16923: Timestamptz always returns utc time when resultformat is in binary format. |
Date: | 2021-03-11 14:18:19 |
Message-ID: | 20210311141819.GE11261@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Mar 11, 2021 at 12:54:11PM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16923
> Logged by: Mark Ford
> Email address: mjfshark(at)gmail(dot)com
> PostgreSQL version: 12.3
> Operating system: Windows 10
> Description:
>
> Tested server version 12.3, client versions 10.13 (32bit and 64bit) and
> 13.2.(64bit)
> Issue:
> Using libpq.dll and requesting a result set in binary format. Timestamptz
> results are returned in UTC timezone instead of the current session's
> timezone setting. Note that in text format the timestamptz is returned
> properly converted. Also note that Timetz results are converted correctly
> regardless of the result set format (binary or text.)
>
> Expected results:
> The documentation seems to state that Timestamptz fields will be returned
> converted to the currently set timezone session property and doesn't mention
> the above behavior. This combined with timetz fields being converted
> regardless of output format seems inconsistent.
I think you need to show us the commands you ran, and their output.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2021-03-11 14:37:19 | Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties |
Previous Message | PG Bug reporting form | 2021-03-11 12:54:11 | BUG #16923: Timestamptz always returns utc time when resultformat is in binary format. |