Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly - Mailing list pgsql-bugs

From Alexander Lakhin
Subject Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
Date
Msg-id 0aaf1cb9-0f85-e786-fb32-b3d68b80d027@gmail.com
Whole thread Raw
In response to BUG #15910: Valgrind-detected error in DecodeTimeOnly  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly  (Alexander Lakhin <exclusion@gmail.com>)
List pgsql-bugs
> Bug reference:      15910
> Logged by:          Alexander Lakhin
> Email address:      exclusion@gmail.com
> PostgreSQL version: 12beta2
> Operating system:   Ubuntu 18.04
> Description:        
>
> When executing the following query:
> SELECT time with time zone '04:05:06 m2';
> I get a strange result:
>       timetz
> -------------------
>  04:05:06+02:30:17
> and the valgrind errors:
> ==00:00:00:07.177 31724== Conditional jump or move depends on uninitialised
> value(s)
> ==00:00:00:07.177 31724==    at 0x57333D: DetermineTimeZoneOffsetInternal
> (datetime.c:1485)
> ==00:00:00:07.177 31724==    by 0x573DA6: DetermineTimeZoneOffset
The attached patch fixes this issue.

Best regards,
Alexander

Attachment

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15911: Why no Bcrypt in pg_hba.conf?
Next
From: PG Bug reporting form
Date:
Subject: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented