From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org, adrian(at)trends(dot)ca |
Subject: | Re: [HACKERS] palloc failures...still... |
Date: | 1998-04-10 17:59:30 |
Message-ID: | Pine.BSF.3.96.980410145424.290C-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 10 Apr 1998, Bruce Momjian wrote:
> > Apr 10 01:59:47 clio radiusd[22585]: query failed: select uniq_id from \
> > radlog where uniq_id='237286618' and stop_time=0 and \
> > term_server='isdn-1.trends.ca';
> > Apr 10 01:59:47 clio radiusd[22585]: query failed: FATAL 1: palloc \
> > failure: memory exhausted
> >
> >
> > And, I'm still getting alot of:
> >
> > FATAL 1: btree: BTP_CHAIN flag was expected
> > FATAL 1: btree: BTP_CHAIN flag was expected
> > FATAL 1: btree: BTP_CHAIN flag was expected
> > FATAL 1: btree: BTP_CHAIN flag was expected
> > FATAL 1: btree: BTP_CHAIN flag was expected
> > FATAL 1: btree: BTP_CHAIN flag was expected
> > FATAL 1: btree: BTP_CHAIN flag was expected
> > FATAL 1: btree: BTP_CHAIN flag was expected
> > FATAL 1: btree: BTP_CHAIN flag was expected
> >
>
> Man, Marc, you get the strangest errors. Time for dump/restore to clean
> up whatever strangeness you have in that database.
that is easier said then done :( the last time I did do that, but
the problem creeped back again...but even ignoring the BTP_CHAIN error,
what about the palloc failure still?
Guess I just found my "release trigger"...this database working
properly :)
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Peter T Mount | 1998-04-10 18:48:29 | Re: [HACKERS] New pg_type for large object |
Previous Message | Bruce Momjian | 1998-04-10 17:31:26 | Re: [HACKERS] palloc failures...still... |