X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.225.181]) by svr1.postgresql.org (Postfix) with ESMTP id 367F3CCE3F for ; Fri, 18 Jul 2003 22:42:21 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr5.postgresql.org [64.117.225.181]) (amavisd-new, port 10024) with ESMTP id 99338-05 for ; Fri, 18 Jul 2003 22:42:40 +0000 (GMT) Received: from ns.minardi.com.mx (ns.minardi.com.mx [148.223.125.238]) by svr1.postgresql.org (Postfix) with ESMTP id A9DA2CCE35 for ; Fri, 18 Jul 2003 19:42:08 -0300 (ADT) Received: from ip030.santarita.intranet (ip030.santarita.intranet [192.168.1.30]) (authenticated (0 bits)) by ns.minardi.com.mx (8.11.6/8.11.6/SuSE Linux 0.5) with ESMTP id h6IMgRH06127 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Fri, 18 Jul 2003 17:42:27 -0500 Subject: Re: [GENERAL] ODBC query problem AGAIN From: Luis =?ISO-8859-1?Q?Maga=F1a?= Reply-To: joe666@gnovus.com To: Maksim Likharev Cc: Postgresql SQL Mail List In-Reply-To: <56510AAEF435D240958D1CE8C6B1770A014A0E63@mailc03.aurigin.com> References: <56510AAEF435D240958D1CE8C6B1770A014A0E63@mailc03.aurigin.com> Content-Type: text/plain; charset=UTF-8 Organization: Gnovus Networks & Software Message-Id: <1058568146.1300.34.camel@kerberus.santarita.intranet> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 18 Jul 2003 17:42:26 -0500 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.12 (www dot roaringpenguin dot com slash mimedefang) X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/265 X-Sequence-Number: 14379 Ok, thanks. I've applied changes to the source, recompiled and tested, everything is working now. Thanks a lot. Regards. On Fri, 2003-07-18 at 16:50, Maksim Likharev wrote: > Try to EXPLAIN SELECT ..., if it crash you most likely have to recompile > postgres with > that strxfrm fix and it's have nothing to do with your data. >=20 > Basically in my case, SunOS 5.8 ( dunno what Solaris version is that, > probably 8 ) > PG was crashing during cost calculation, long before any data access. >=20 >=20 >=20 > -----Original Message----- > From: Luis Maga=C3=B1a [mailto:joe666@gnovus.com] > Sent: Friday, July 18, 2003 2:43 PM > To: Maksim Likharev > Cc: Postgresql General Mail List > Subject: ODBC query problem AGAIN >=20 >=20 > Hi, >=20 > After having moved all of the data to a new database initializaed with > es_MX as locale, the postmaster is dying and restarting every time a > program tries to read information on this tables: >=20 > pg_catalog.pg_class > pg_catalog.pg_namespace >=20 > it is important to note that if I do a simple select * from table with > either one of them server do not crash at all, the problem seems to > happen only when joining. >=20 > Another important point is that my problems started after I ran vacuumdb > -z on the database, or at least that's what I think. >=20 > Have tried this with psql, dbvisualizer and ODBC driver in windows. >=20 > One of the crashing queries is: >=20 > SELECT > n.nspname,c.relname,a.attname,a.atttypid,a.attnotnull,a.atttypmod,a.attl > en,a.attnum,def.adsrc,dsc.description FROM pg_catalog.pg_namespace n > JOIN pg_catalog.pg_class c ON (c.relnamespace =3D n.oid) JOIN > pg_catalog.pg_attribute a ON (a.attrelid=3Dc.oid) LEFT JOIN > pg_catalog.pg_attrdef def ON (a.attrelid=3Ddef.adrelid AND a.attnum =3D > def.adnum) LEFT JOIN pg_catalog.pg_description dsc ON (c.oid=3Ddsc.objoid > AND a.attnum =3D dsc.objsubid) LEFT JOIN pg_catalog.pg_class dc ON > (dc.oid=3Ddsc.classoid AND dc.relname=3D'pg_class') LEFT JOIN > pg_catalog.pg_namespace dn ON (dc.relnamespace=3Ddn.oid AND > dn.nspname=3D'pg_catalog') WHERE a.attnum > 0 AND NOT a.attisdropped AND > n.nspname LIKE 'public' AND c.relname LIKE 'catalogo_empaque' AND > a.attname LIKE '%' ORDER BY nspname,relname,attname >=20 > The Log Output after that query is: >=20 > 2003-07-18 16:34:59 [9127] LOG: server process (pid 9131) was > terminated by signal 10 > 2003-07-18 16:34:59 [9127] LOG: terminating any other active server > processes > 2003-07-18 16:34:59 [9127] LOG: all server processes terminated; > reinitializing shared memory and semaphores > 2003-07-18 16:34:59 [9134] LOG: database system was interrupted at > 2003-07-18 16:32:58 CDT > 2003-07-18 16:34:59 [9134] LOG: checkpoint record is at 0/2F4DAC30 > 2003-07-18 16:34:59 [9134] LOG: redo record is at 0/2F4DAC30; undo > record is at 0/0; shutdown TRUE > 2003-07-18 16:34:59 [9134] LOG: next transaction id: 8808; next oid: > 1833525 > 2003-07-18 16:34:59 [9134] LOG: database system was not properly shut > down; automatic recovery in progress > 2003-07-18 16:34:59 [9134] LOG: ReadRecord: record with zero length > at 0/2F4DAC70 > 2003-07-18 16:34:59 [9134] LOG: redo is not required > 2003-07-18 16:35:02 [9134] LOG: database system is ready >=20 > Plataform is Solaris 8, running on Sparc compiled with 32bit only, no > core is dumped by the crashing processes. >=20 > Any new suggestions ?, I will try locale 'C' when moving data to new > database. >=20 > Regards. --=20 Luis Maga=C3=B1a. Gnovus Networks & Software. www.gnovus.com