Re: Git-master regression failure - Mailing list pgsql-hackers
| From | Svenne Krap |
|---|---|
| Subject | Re: Git-master regression failure |
| Date | |
| Msg-id | 51C0A4D0.7080804@krap.dk Whole thread Raw |
| In response to | Git-master regression failure (Svenne Krap <svenne.lists@krap.dk>) |
| Responses |
Re: Git-master regression failure
|
| List | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 18-06-2013 18:40, Svenne Krap wrote:
> Any ideas what might have happened?
After doing some more digging...
My laptop (which runs PostgreSQL 9.2.4 on x86_64-pc-linux-gnu, compiled
by x86_64-pc-linux-gnu-gcc (Gentoo 4.7.3 p1.0, pie-0.5.5) 4.7.3,
64-bit) also returns "99", if I
- - run the CREATE TABLE tenk1 (from the git-master)
- - load data from tenk.data (from git-master)
- - run the "offending part" of the create_index.sql (also from git-master):
The offending offending_part is:
CREATE TABLE dupindexcols
AS SELECT unique1 as id, stringu2::text as f1 FROM
tenk1;
CREATE INDEX dupindexcols_i ON dupindexcols (f1, id, f1
text_pattern_ops);
ANALYZE
dupindexcols;
EXPLAIN (COSTS
OFF)
SELECT count(*) FROM
dupindexcols WHERE f1 > 'WA' and id < 1000 and f1 ~<~
'YX';
SELECT count(*) FROM
dupindexcols WHERE f1 > 'WA' and id < 1000 and f1 ~<~ 'YX';
As I have no real idea of what "~<~" is for an operator (I have looked
it up as scalarltjoinsel), but I cannot find any semantics for it in the
docs*... So I have no way of manually checking the expected result.
*=The term ~<~ is not exactly google-friendly and the docs site's search
also returns empty...
Anyone has any idea what to look after next?
Svenne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQI5BAEBCAAjBQJRwKTQHBpodHRwOi8vc3Zlbm5lLmRrL3BncC9wb2xpY3kACgkQ
/zLSj+olL/KGHQ//d5WM2gi4yIaMCpaij1+PdCzBwyMwz0E3Ys4mlj1x7x22v8ty
6Gs6HZlofuuUdBkhDvRYYvbJ8asdi51KbjVMbrBkR49txiM00cWLtT74e9mFdTaA
f5lOeUmfyqy7O9jlyFvKaC8hVRe7yQrbRK+b2sOBIq2TchVkvjT/AvvDcuPWCKD7
6FgHOtFF4Ae4yqC6foylfBQ59TpOYHBd+ohl38egtDr87tXSXcuIU1bNZeJfqcPM
rs02h8L/kmWrx32TmYKLUw6PdluPEJ2WB5Gcsd8Va5p7ai3+rbqzzJGw9ZOFkPv4
9ruTqjTV0l7xhwuztHpSCTiyOoV0dIw13USTO7D/rAseqIUgb0mQE4cXVQW9GVT1
WjCqnaqRwdgYnvke7jtOfX2AeiZjluZfF1e2B2rVMfDan1A5PxjLmxpzH7fYs0bs
RDEnOx9bcVUYH6xedVyYHbSmx7GXyzu0xfADsWgsYNclv91cZ5pz9+fwJv8ceNNz
ckOcA4DlKeo1fw0idvbEUtVWf/tO8H6r0heNuMgR5M6qOtlbsLsdsJvOIUTzGn7W
oxikvMAKbAX0Hl4arQSQE5Og7HcLsEB6YaMp0bpj55Y4prr/fhzJHKL4ioCI6NOH
gLknu+IPDyJiNez4QqaqAITDtxo+68euv5uUE+O55o9ssBEWoTX0bz8trM8=
=2IBo
-----END PGP SIGNATURE-----
pgsql-hackers by date: