BTW, I forgot to mention that I did experiment with your python-based
test script for pg_stat_statements, but decided not to commit it.
There are just too many external dependencies for my taste:
3. dellstore2 test database
That coupled with the apparent impossibility of running the script
without manual preconfiguration makes it look not terribly useful.
Also, as of the committed patch there are several individual tests that
fail or need adjustment:
The SELECT INTO tests all fail, but we know the reason why (the testbed
isn't expecting them to result in creating separate entries for the
utility statement and the underlying plannable SELECT).
verify_statement_equivalency("select a.orderid from orders a join orders b on a.orderid = b.orderid",
"select b.orderid from orders a join orders b on a.orderid = b.orderid", conn)
These are not equivalent statements, or at least would not be if the
join condition were anything else than what it is, so the fact that the
original coding failed to distinguish the targetlist entries is a bug.
# temporary column name within recursive CTEs doesn't differentiate
fails, not because of the change of column name, but because of the
change of CTE name. This is a consequence of my having used the CTE
* Depending on the CTE name here isn't ideal, but it's the
* only info we have to identify the referenced WITH item.
We could avoid the name dependency by omitting ctename from the jumble
but I think that cure is worse than the disease.
Anyway, not too important, but I just thought I'd document this in case
you were wondering about the discrepancies.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2012-03-29 02:45:00|
|Subject: Re: Re: [COMMITTERS] pgsql: pg_test_timing utility, to measure clock monotonicity and timing |
|Previous:||From: Fujii Masao||Date: 2012-03-29 02:33:04|
|Subject: Re: Re: [COMMITTERS] pgsql: pg_test_timing utility, to
measure clock monotonicity and timing|