Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements

From: Greg Stark <stark(at)mit(dot)edu>
To: Andrei Zubkov <zubkov(at)moonset(dot)ru>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "Anton A(dot) Melnikov" <aamelnikov(at)inbox(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements
Date: 2022-04-02 21:38:35
Message-ID: CAM-w4HOPwBYHi5Eyqzk4pXLFCVmeQ1s5_zy2am=d4z+=QDaEwA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The tests for this seem to need adjustments.

[12:41:09.403] test pg_stat_statements ... FAILED 180 ms

diff -U3 /tmp/cirrus-ci-build/contrib/pg_stat_statements/expected/pg_stat_statements.out
/tmp/cirrus-ci-build/contrib/pg_stat_statements/results/pg_stat_statements.out
--- /tmp/cirrus-ci-build/contrib/pg_stat_statements/expected/pg_stat_statements.out
2022-04-02 12:37:42.201823383 +0000
+++ /tmp/cirrus-ci-build/contrib/pg_stat_statements/results/pg_stat_statements.out
2022-04-02 12:41:09.219563204 +0000
@@ -1174,8 +1174,8 @@
ORDER BY query;
query | reset_ts_match
---------------------------+----------------
- SELECT $1,$2 AS "STMTTS2" | f
SELECT $1 AS "STMTTS1" | t
+ SELECT $1,$2 AS "STMTTS2" | f
(2 rows)

-- check that minmax reset does not set stats_reset

Hm. Is this a collation problem?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2022-04-02 21:45:13 Re: A qsort template
Previous Message Andres Freund 2022-04-02 21:03:33 Re: A qsort template