Received: from lectoure.ghs.fr (IDENT:root@e009.paris-88.cybercable.fr [212.198.88.9]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA31096; Fri, 28 Jan 2000 17:31:38 -0500 (EST) (envelope-from nhuillard@ghs.fr) Received: from agen.int.ghs (agen.int.ghs [192.168.200.21]) by lectoure.ghs.fr (8.8.7/8.8.7) with SMTP id XAA00388; Fri, 28 Jan 2000 23:31:36 +0100 Received: by agen.int.ghs with Microsoft Mail id <01BF69E7.D17FF8D0@agen.int.ghs>; Fri, 28 Jan 2000 23:31:36 +0100 Message-ID: <01BF69E7.D17FF8D0@agen.int.ghs> From: Nicolas Huillard To: "pgsql-general@hub.org" , "pgsql-sql@hub.org" Subject: RE: [SQL] RE: [GENERAL] Problem with SELECT on large negative INT4 Date: Fri, 28 Jan 2000 23:31:34 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id RAB31122 A little adjustment : SOME queries work with the new binary and the old indexes. Many other don't, as Tom and Hiroshi figured. With a new binary and after reloding the DB, every seems to work correctly. Nicolas Huillard -----Message d'origine----- De: Nicolas Huillard [SMTP:nhuillard@ghs.fr] Date: vendredi 28 janvier 2000 22:42 À: pgsql-general@hub.org; pgsql-sql@hub.org Objet: RE: [SQL] RE: [GENERAL] Problem with SELECT on large negative INT4 Thank to everybody, I recompiled Postgres and tested it on the same DB : the offending SELECT worked, without any index regeneration. Maybe the order in which the items where inserted in the table (using COPY, before creating the index) made it working. ...