Re: [GENERAL] ODBC query problem AGAIN - Mailing list pgsql-sql

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.
>
> 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.
>
>
>
> -----Original Message-----
> From: Luis Magaña [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
>
>
> Hi,
>
> 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:
>
> pg_catalog.pg_class
> pg_catalog.pg_namespace
>
> 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.
>
> Another important point is that my problems started after I ran vacuumdb
> -z on the database, or at least that's what I think.
>
> Have tried this with psql, dbvisualizer and ODBC driver in windows.
>
> One of the crashing queries is:
>
> 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 = n.oid) JOIN
> pg_catalog.pg_attribute a ON (a.attrelid=c.oid)  LEFT JOIN
> pg_catalog.pg_attrdef def ON (a.attrelid=def.adrelid AND a.attnum =
> def.adnum)  LEFT JOIN pg_catalog.pg_description dsc ON (c.oid=dsc.objoid
> AND a.attnum = dsc.objsubid)  LEFT JOIN pg_catalog.pg_class dc ON
> (dc.oid=dsc.classoid AND dc.relname='pg_class')  LEFT JOIN
> pg_catalog.pg_namespace dn ON (dc.relnamespace=dn.oid AND
> dn.nspname='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
>
> The Log Output after that query is:
>
> 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
>
> Plataform is Solaris 8, running on Sparc compiled with 32bit only, no
> core is dumped by the crashing processes.
>
> Any new suggestions ?, I will try locale 'C' when moving data to new
> database.
>
> Regards.
--
Luis Magaña.
Gnovus Networks & Software.
www.gnovus.com