Re: reindex vs. drop index , create index

hello,

I am currently using 7.3.1 -- planning to upgrade soon....

sorry, I didn't save nor log the exact error message.

using a SuSE Linux with kernel 2.4.20


--

Mit freundlichem Gruß

Henrik Steffen
Geschäftsführer

top concepts Internetmarketing GmbH
Am Steinkamp 7 - D-21684 Stade - Germany
--------------------------------------------------------
http://www.topconcepts.com          Tel. +49 4141 991230
mail: steffen@topconcepts.com       Fax. +49 4141 991233
--------------------------------------------------------
24h-Support Hotline:  +49 1908 34697 (EUR 1.86/Min,topc)
--------------------------------------------------------
Ihr SMS-Gateway: JETZT NEU unter: http://sms.city-map.de
System-Partner gesucht: http://www.franchise.city-map.de
--------------------------------------------------------
Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
--------------------------------------------------------

----- Original Message -----
From: "Neil Conway" <neilc@samurai.com>
To: "Henrik Steffen" <steffen@city-map.de>
Cc: "PostgreSQL General" <pgsql-general@postgresql.org>
Sent: Friday, February 21, 2003 7:40 AM
Subject: Re: [GENERAL] reindex vs. drop index , create index


> On Thu, 2003-02-20 at 12:03, Henrik Steffen wrote:
> > a few weeks ago I turned to REINDEXing my tables instead of DROPping and
> > reCREATEing them.
> >
> > now, however, I again have problems when VACUUMing or REINDEXing these
> > tables. Postgres states that the connection has been lost etc.
>
> Can you provide the exact error message, as well as the version of
> PostgreSQL you're using and any relevant OS version details.
>
> Also, it sounds like PostgreSQL might be dumping core. If that's the
> case, providing a backtrace from the core file (using gdb) would be
> helpful. It would be especially helpful if you could recompile
> PostgreSQL with debugging symbols (./configure --enable-debug) and get a
> backtrace after that.
>
> Cheers,
>
> Neil
> --
> Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC
>
>
>