Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA02472; Wed, 24 Jun 92 08:38:58 -0700
Message-Id: <9206241538.AA02472@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: R-tree problem (the continuing story)
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Reply-To: mer@postgres.berkeley.edu
In-Reply-To: Your message of "Wed, 24 Jun 92 12:41:25 +0700."
             <9206241037.AA00209@postgres.Berkeley.EDU> 
Date: Wed, 24 Jun 92 08:38:44 PDT

you write:

> This is very nice, but there is still a problem left. I've already
> asked this before but I didn't get any answers. When I define a index
> first and than add all the tuples, everything is going fine. But when
> I first add all the tuples and create an index afterwards, the size of the
> postgres backend grows extremely and finally terminates with a core dump.
> What is going wrong. 

Vincent,

As I understand it, Mike is working on your latest but report.  We, in general,
don't respond to bug reports unless we have fixed the bug.  The bugs account
is set up to send an acknowledgement to incoming messages so that
people know we are receiving them (this doesn't apply to messages sent
to the mailing list).  If you get an acknowledgement, then you can be sure
that we will be looking at the problem.  You will have to be patient with us,
as we are extremely busy at present.


Jeff Meredith
mer@postgres.berkeley.edu