Skip site navigation (1) Skip section navigation (2)

Re: [BUGS] problem creating index in 6,5,3

From: Karl DeBisschop <kdebisschop(at)range(dot)infoplease(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: [BUGS] problem creating index in 6,5,3
Date: 1999-12-17 21:38:54
Message-ID: 199912172138.QAA07500@skillet.infoplease.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-general
Recompiled with

  (a) add --enable-cassert to the configure command;
  (b) do   make COPT=-g all  instead of just make all.

On the same machine that the backend runs on.

Still same behaviour.  Saw small notice in log file:

proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)
proc_exit(0) [#0]
shmem_exit(0) [#0]
exit(0)

Still no core.

I'm not really sure there is a linkage with the ordering thing -
remember that this worked fine a week ago before I upgraded to 6.5.3.
Unless the backend reaches out to different libraries than in 6.5.1, I
think it's unlikely to be RH6n libraries.  Also, even tough RH libs
can be odd, this is not a redhat machine - it's VA linux, which uses
RPMs but is in many aspects different than VA linux.

So I'm still stumped.  For laughs, I think I'll try it on a much less
powerful RH60 box and see what I get.

Let me know if there's anything else I can do to help diagnose.

Karl

In response to

pgsql-bugs by date

Next:From: Laurent LEVIERDate: 1999-12-17 22:09:49
Subject: PostregSQL 6.5.3 on Linux RedHat 6.1/Ultra1 Sparc (sun4u)
Previous:From: Karl DeBisschopDate: 1999-12-17 19:16:46
Subject: Re: [BUGS] problem creating index in 6,5,3

pgsql-general by date

Next:From: adminDate: 1999-12-17 22:17:03
Subject: hash taboo?
Previous:From: Culberson, PhilipDate: 1999-12-17 19:45:46
Subject: RE: [GENERAL] How to get timestamped pgsql logging?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group