Subject: Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
From: Alexander Lakhin <exclusion@gmail.com>
To: pgsql-bugs@lists.postgresql.org
References: <15910-2eba5106b9aa0c61@postgresql.org>
 <0aaf1cb9-0f85-e786-fb32-b3d68b80d027@gmail.com>
Message-ID: <97ac4fe2-65d9-6a7b-76e0-5ad3b06cd9dc@gmail.com>
Date: Mon, 5 Aug 2019 08:55:55 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <0aaf1cb9-0f85-e786-fb32-b3d68b80d027@gmail.com>
Content-Type: multipart/mixed;
 boundary="------------66E49616F7563FC7EE9EF201"
Content-Language: en-US
Precedence: bulk

This is a multi-part message in MIME format.
--------------66E49616F7563FC7EE9EF201
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hello hackers,

16.07.2019 19:24, Alexander Lakhin wrote:
>> 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
>>
> The attached patch fixes this issue.
In case this bug is worth fixing, please look at the improved patch with
the corresponding regression test.

Best regards,
Alexander

--------------66E49616F7563FC7EE9EF201
Content-Type: text/x-patch;
 name="fix-DecodeTimeOnly-v2.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="fix-DecodeTimeOnly-v2.patch"

diff --git a/src/backend/utils/adt/datetime.c b/src/backend/utils/adt/datetime.c
index 972fcd26a2..1f8b0183f3 100644
--- a/src/backend/utils/adt/datetime.c
+++ b/src/backend/utils/adt/datetime.c
@@ -2280,6 +2280,9 @@ DecodeTimeOnly(char **field, int *ftype, int nf,
 			GetCurrentDateTime(tmp);
 		else
 		{
+			/* a date has to be fully specified */
+			if ((fmask & DTK_DATE_M) != DTK_DATE_M)
+				return DTERR_BAD_FORMAT;
 			tmp->tm_year = tm->tm_year;
 			tmp->tm_mon = tm->tm_mon;
 			tmp->tm_mday = tm->tm_mday;
@@ -2307,6 +2310,9 @@ DecodeTimeOnly(char **field, int *ftype, int nf,
 			GetCurrentDateTime(tmp);
 		else
 		{
+			/* a date has to be fully specified */
+			if ((fmask & DTK_DATE_M) != DTK_DATE_M)
+				return DTERR_BAD_FORMAT;
 			tmp->tm_year = tm->tm_year;
 			tmp->tm_mon = tm->tm_mon;
 			tmp->tm_mday = tm->tm_mday;
diff --git a/src/test/regress/expected/timetz.out b/src/test/regress/expected/timetz.out
index 33ff8e18c9..32609dfdc8 100644
--- a/src/test/regress/expected/timetz.out
+++ b/src/test/regress/expected/timetz.out
@@ -19,6 +19,11 @@ INSERT INTO TIMETZ_TBL VALUES ('15:36:39 America/New_York');
 ERROR:  invalid input syntax for type time with time zone: "15:36:39 America/New_York"
 LINE 1: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 America/New_York');
                                        ^
+-- this should fail (the time specification is invalid)
+INSERT INTO TIMETZ_TBL VALUES ('15:36:39 m2');
+ERROR:  invalid input syntax for type time with time zone: "15:36:39 m2"
+LINE 1: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 m2');
+                                       ^
 SELECT f1 AS "Time TZ" FROM TIMETZ_TBL;
     Time TZ     
 ----------------
diff --git a/src/test/regress/sql/timetz.sql b/src/test/regress/sql/timetz.sql
index c41686a5e2..a0a7cc4eb2 100644
--- a/src/test/regress/sql/timetz.sql
+++ b/src/test/regress/sql/timetz.sql
@@ -19,6 +19,9 @@ INSERT INTO TIMETZ_TBL VALUES ('2003-03-07 15:36:39 America/New_York');
 INSERT INTO TIMETZ_TBL VALUES ('2003-07-07 15:36:39 America/New_York');
 -- this should fail (the timezone offset is not known)
 INSERT INTO TIMETZ_TBL VALUES ('15:36:39 America/New_York');
+-- this should fail (the time specification is invalid)
+INSERT INTO TIMETZ_TBL VALUES ('15:36:39 m2');
+
 
 SELECT f1 AS "Time TZ" FROM TIMETZ_TBL;
 

--------------66E49616F7563FC7EE9EF201--