| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | adrian(at)trends(dot)ca |
| Subject: | palloc failures...still... |
| Date: | 1998-04-10 16:20:35 |
| Message-ID: | Pine.BSF.3.96.980410131429.290B-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Morning everyone...
After upgrading the server to -current, which is meant for
release on April 15th, I'm still receiving a palloc() failure, as shown
below.
The server is a 486DX with 64Meg of RAM, and the able that is
being searched is *only* 5k records large...and the query below will
return *only* 1 of those records...
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-04-10 17:31:26 | Re: [HACKERS] palloc failures...still... |
| Previous Message | Kent S. Gordon | 1998-04-10 15:32:38 | Re: [HACKERS] New pg_type for large object |