pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #15910: Valgrind-detected error in DecodeTimeOnly
8+ messages / 3 participants
[nested] [flat]
Commits from this thread:
2019-08-07 64579be64a d8652ec555 d16d241a55 1ba4d0fe46 7c64a2cd94 1de3e0589a 1f79436981 Fix some incorrect parsing of time with time zone strings
* BUG #15910: Valgrind-detected error in DecodeTimeOnly
@ 2019-07-16 16:19 PG Bug reporting form <noreply@postgresql.org>
2019-07-16 16:24 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
0 siblings, 1 reply; 8+ messages in thread
From: PG Bug reporting form @ 2019-07-16 16:19 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: exclusion@gmail.com
The following bug has been logged on the website:
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
(datetime.c:1445)
==00:00:00:07.177 31724== by 0x575FEE: DecodeTimeOnly (datetime.c:2317)
==00:00:00:07.177 31724== by 0x570D6B: timetz_in (date.c:1994)
==00:00:00:07.177 31724== by 0x67356B: InputFunctionCall (fmgr.c:1548)
==00:00:00:07.177 31724== by 0x67378C: OidInputFunctionCall
(fmgr.c:1651)
==00:00:00:07.177 31724== by 0x30C312: stringTypeDatum
(parse_type.c:641)
==00:00:00:07.177 31724== by 0x2F282F: coerce_type (parse_coerce.c:304)
==00:00:00:07.177 31724== by 0x2F1B15: coerce_to_target_type
(parse_coerce.c:103)
==00:00:00:07.177 31724== by 0x2F8E4A: transformTypeCast
(parse_expr.c:2813)
==00:00:00:07.177 31724== by 0x2F83F8: transformExprRecurse
(parse_expr.c:202)
==00:00:00:07.177 31724== by 0x2F807F: transformExpr (parse_expr.c:155)
==00:00:00:07.177 31724== Uninitialised value was created by a stack
allocation
==00:00:00:07.177 31724== at 0x570C8E: timetz_in (date.c:1972)
==00:00:00:07.177 31724==
...
==00:00:00:07.179 31724== Conditional jump or move depends on uninitialised
value(s)
==00:00:00:07.179 31724== at 0x6B2165: pg_next_dst_boundary
(localtime.c:1698)
==00:00:00:07.179 31724== by 0x573447: DetermineTimeZoneOffsetInternal
(datetime.c:1508)
==00:00:00:07.179 31724== by 0x573DA6: DetermineTimeZoneOffset
(datetime.c:1445)
==00:00:00:07.179 31724== by 0x575FEE: DecodeTimeOnly (datetime.c:2317)
==00:00:00:07.179 31724== by 0x570D6B: timetz_in (date.c:1994)
==00:00:00:07.179 31724== by 0x67356B: InputFunctionCall (fmgr.c:1548)
==00:00:00:07.179 31724== by 0x67378C: OidInputFunctionCall
(fmgr.c:1651)
==00:00:00:07.179 31724== by 0x30C312: stringTypeDatum
(parse_type.c:641)
==00:00:00:07.179 31724== by 0x2F282F: coerce_type (parse_coerce.c:304)
==00:00:00:07.179 31724== by 0x2F1B15: coerce_to_target_type
(parse_coerce.c:103)
==00:00:00:07.179 31724== by 0x2F8E4A: transformTypeCast
(parse_expr.c:2813)
==00:00:00:07.179 31724== by 0x2F83F8: transformExprRecurse
(parse_expr.c:202)
==00:00:00:07.180 31724== Uninitialised value was created by a stack
allocation
==00:00:00:07.180 31724== at 0x570C8E: timetz_in (date.c:1972)
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
2019-07-16 16:19 BUG #15910: Valgrind-detected error in DecodeTimeOnly PG Bug reporting form <noreply@postgresql.org>
@ 2019-07-16 16:24 ` Alexander Lakhin <exclusion@gmail.com>
2019-08-05 05:55 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
0 siblings, 1 reply; 8+ messages in thread
From: Alexander Lakhin @ 2019-07-16 16:24 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org
> 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
Attachments:
fix-DecodeTimeOnly.patch (text/x-patch, 842B) download
diff --git a/src/backend/utils/adt/datetime.c b/src/backend/utils/adt/datetime.c
index 54ea69f7f1..0a13ec8492 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;
* Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
2019-07-16 16:19 BUG #15910: Valgrind-detected error in DecodeTimeOnly PG Bug reporting form <noreply@postgresql.org>
2019-07-16 16:24 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
@ 2019-08-05 05:55 ` Alexander Lakhin <exclusion@gmail.com>
2019-08-06 06:21 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Michael Paquier <michael@paquier.xyz>
0 siblings, 1 reply; 8+ messages in thread
From: Alexander Lakhin @ 2019-08-05 05:55 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org
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
Attachments:
fix-DecodeTimeOnly-v2.patch (text/x-patch, 2.3K) download
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;
* Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
2019-07-16 16:19 BUG #15910: Valgrind-detected error in DecodeTimeOnly PG Bug reporting form <noreply@postgresql.org>
2019-07-16 16:24 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
2019-08-05 05:55 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
@ 2019-08-06 06:21 ` Michael Paquier <michael@paquier.xyz>
2019-08-06 06:24 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Michael Paquier <michael@paquier.xyz>
2019-08-07 04:12 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
0 siblings, 2 replies; 8+ messages in thread
From: Michael Paquier @ 2019-08-06 06:21 UTC (permalink / raw)
To: Alexander Lakhin <exclusion@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
On Mon, Aug 05, 2019 at 08:55:55AM +0300, Alexander Lakhin wrote:
> In case this bug is worth fixing, please look at the improved patch with
> the corresponding regression test.
In this case, DecodeSpecial() decodes the abbrevation passed down as
UNITS, which is right on its own. Still, afterwards the code fails to
correctly set a date from the string present. In short, your
suggestion of fix looks good to me and that's more consistent with the
full timezone spec case. The test case you added in this patch
triggers the error in the code path where the timezone is not
specified. Could you add an extra test case for the timezone
abbreviation?
Note that the next set of minor versions is very close by (we are in a
cease-fire period for commits on back-branches), so this won't be
fixed in the upcoming releases.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
2019-07-16 16:19 BUG #15910: Valgrind-detected error in DecodeTimeOnly PG Bug reporting form <noreply@postgresql.org>
2019-07-16 16:24 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
2019-08-05 05:55 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
2019-08-06 06:21 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Michael Paquier <michael@paquier.xyz>
@ 2019-08-06 06:24 ` Michael Paquier <michael@paquier.xyz>
2019-08-07 04:29 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
1 sibling, 1 reply; 8+ messages in thread
From: Michael Paquier @ 2019-08-06 06:24 UTC (permalink / raw)
To: Alexander Lakhin <exclusion@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
On Tue, Aug 06, 2019 at 03:21:11PM +0900, Michael Paquier wrote:
> Note that the next set of minor versions is very close by (we are in a
> cease-fire period for commits on back-branches), so this won't be
> fixed in the upcoming releases.
By the way, as long as I do not forget, could you add this patch to
the next CF [1] as a bug fix? It is fine to add me as a reviewer.
[1]: https://commitfest.postgresql.org/24/
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
2019-07-16 16:19 BUG #15910: Valgrind-detected error in DecodeTimeOnly PG Bug reporting form <noreply@postgresql.org>
2019-07-16 16:24 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
2019-08-05 05:55 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
2019-08-06 06:21 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Michael Paquier <michael@paquier.xyz>
2019-08-06 06:24 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Michael Paquier <michael@paquier.xyz>
@ 2019-08-07 04:29 ` Alexander Lakhin <exclusion@gmail.com>
0 siblings, 0 replies; 8+ messages in thread
From: Alexander Lakhin @ 2019-08-07 04:29 UTC (permalink / raw)
To: Michael Paquier <michael@paquier.xyz>; +Cc: pgsql-bugs@lists.postgresql.org
06.08.2019 9:24, Michael Paquier wrote:
> On Tue, Aug 06, 2019 at 03:21:11PM +0900, Michael Paquier wrote:
>> Note that the next set of minor versions is very close by (we are in a
>> cease-fire period for commits on back-branches), so this won't be
>> fixed in the upcoming releases.
> By the way, as long as I do not forget, could you add this patch to
> the next CF [1] as a bug fix? It is fine to add me as a reviewer.
>
> [1]: https://commitfest.postgresql.org/24/
Thank you Michael. It's done:
https://commitfest.postgresql.org/24/2231/
Best regards,
Alexander
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
2019-07-16 16:19 BUG #15910: Valgrind-detected error in DecodeTimeOnly PG Bug reporting form <noreply@postgresql.org>
2019-07-16 16:24 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
2019-08-05 05:55 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
2019-08-06 06:21 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Michael Paquier <michael@paquier.xyz>
@ 2019-08-07 04:12 ` Alexander Lakhin <exclusion@gmail.com>
2019-08-07 09:54 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Michael Paquier <michael@paquier.xyz>
1 sibling, 1 reply; 8+ messages in thread
From: Alexander Lakhin @ 2019-08-07 04:12 UTC (permalink / raw)
To: Michael Paquier <michael@paquier.xyz>; +Cc: pgsql-bugs@lists.postgresql.org
Hello Michael,
06.08.2019 9:21, Michael Paquier wrote:
> On Mon, Aug 05, 2019 at 08:55:55AM +0300, Alexander Lakhin wrote:
>> In case this bug is worth fixing, please look at the improved patch with
>> the corresponding regression test.
> In this case, DecodeSpecial() decodes the abbrevation passed down as
> UNITS, which is right on its own. Still, afterwards the code fails to
> correctly set a date from the string present. In short, your
> suggestion of fix looks good to me and that's more consistent with the
> full timezone spec case. The test case you added in this patch
> triggers the error in the code path where the timezone is not
> specified. Could you add an extra test case for the timezone
> abbreviation?
Sure, please look at the improved fix.
Best regards,
Alexander
Attachments:
fix-DecodeTimeOnly-v3.patch (text/x-patch, 2.7K) download
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..a25f468cbb 100644
--- a/src/test/regress/expected/timetz.out
+++ b/src/test/regress/expected/timetz.out
@@ -19,6 +19,16 @@ 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');
+ ^
+-- this should fail too (the same with a dynamic timezone abbreviation)
+INSERT INTO TIMETZ_TBL VALUES ('15:36:39 MSK m2');
+ERROR: invalid input syntax for type time with time zone: "15:36:39 MSK m2"
+LINE 1: INSERT INTO TIMETZ_TBL VALUES ('15:36:39 MSK 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..58c4b6e1bc 100644
--- a/src/test/regress/sql/timetz.sql
+++ b/src/test/regress/sql/timetz.sql
@@ -19,6 +19,11 @@ 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');
+-- this should fail too (the same with a dynamic timezone abbreviation)
+INSERT INTO TIMETZ_TBL VALUES ('15:36:39 MSK m2');
+
SELECT f1 AS "Time TZ" FROM TIMETZ_TBL;
* Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly
2019-07-16 16:19 BUG #15910: Valgrind-detected error in DecodeTimeOnly PG Bug reporting form <noreply@postgresql.org>
2019-07-16 16:24 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
2019-08-05 05:55 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
2019-08-06 06:21 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Michael Paquier <michael@paquier.xyz>
2019-08-07 04:12 ` Re: BUG #15910: Valgrind-detected error in DecodeTimeOnly Alexander Lakhin <exclusion@gmail.com>
@ 2019-08-07 09:54 ` Michael Paquier <michael@paquier.xyz>
0 siblings, 0 replies; 8+ messages in thread
From: Michael Paquier @ 2019-08-07 09:54 UTC (permalink / raw)
To: Alexander Lakhin <exclusion@gmail.com>; +Cc: pgsql-bugs@lists.postgresql.org
On Wed, Aug 07, 2019 at 07:12:48AM +0300, Alexander Lakhin wrote:
> Sure, please look at the improved fix.
Thanks Alexander. I have been able to look at that today, and applied
the patch down to 9.4, after testing each branch. Valgrind was
complaining all the way down..
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2019-08-07 09:54 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-07-16 16:19 BUG #15910: Valgrind-detected error in DecodeTimeOnly PG Bug reporting form <noreply@postgresql.org>
2019-07-16 16:24 ` Alexander Lakhin <exclusion@gmail.com>
2019-08-05 05:55 ` Alexander Lakhin <exclusion@gmail.com>
2019-08-06 06:21 ` Michael Paquier <michael@paquier.xyz>
2019-08-06 06:24 ` Michael Paquier <michael@paquier.xyz>
2019-08-07 04:29 ` Alexander Lakhin <exclusion@gmail.com>
2019-08-07 04:12 ` Alexander Lakhin <exclusion@gmail.com>
2019-08-07 09:54 ` Michael Paquier <michael@paquier.xyz>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox