diff options
| author | Michael Paquier <michael@paquier.xyz> | 2019-08-07 18:16:31 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2019-08-07 18:16:31 +0900 |
| commit | 64579be64a3811d08ea7ccf92b1a443d76b96412 (patch) | |
| tree | 02e08a34fd14fede5391b9beae93f57af83a6421 /src/backend/parser/parse_utilcmd.c | |
| parent | 75c1921cd6c868c5995b88113b4463a4830b9a27 (diff) | |
| download | postgresql-64579be64a3811d08ea7ccf92b1a443d76b96412.tar.gz postgresql-64579be64a3811d08ea7ccf92b1a443d76b96412.zip | |
Fix some incorrect parsing of time with time zone strings
When parsing a timetz string with a dynamic timezone abbreviation or a
timezone not specified, it was possible to generate incorrect timestamps
based on a date which uses some non-initialized variables if the input
string did not specify fully a date to parse. This is already checked
when a full timezone spec is included in the input string, but the two
other cases mentioned above missed the same checks.
This gets fixed by generating an error as this input is invalid, or in
short when a date is not fully specified.
Valgrind was complaining about this problem.
Bug: #15910
Author: Alexander Lakhin
Discussion: https://postgr.es/m/15910-2eba5106b9aa0c61@postgresql.org
Backpatch-through: 9.4
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions