Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
Date: 2019-07-16 16:24:56
Message-ID: 0aaf1cb9-0f85-e786-fb32-b3d68b80d027@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> Bug reference: 15910
> Logged by: Alexander Lakhin
> Email address: exclusion(at)gmail(dot)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 Content-Type Size
fix-DecodeTimeOnly.patch text/x-patch 843 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-07-16 16:26:54 BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
Previous Message PG Bug reporting form 2019-07-16 16:23:29 BUG #15911: Why no Bcrypt in pg_hba.conf?