From: | "Christian Brosig" <Brosig(at)dataconsult(dot)de> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Gaetano Mendola'" <mendola(at)bigfoot(dot)com> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Out of buffer error |
Date: | 2003-11-10 07:33:10 |
Message-ID: | !~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAHPiM5TNZ80Ohrzn55tUApMKAAAAQAAAAeHIa6wnGBEaS3/+Kzyp9/QEAAAAA@dataconsult.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I am running 7.3.2.
I will update to 7.3.4 as soon as possible.
If the problem is still there after the update, I will post once more
the issue.
Thank you for your help
Best Regards
Christian Brosig
Gaetano Mendola <mendola(at)bigfoot(dot)com> writes:
> Tom Lane wrote:
>> "Christian Brosig" <Brosig(at)dataconsult(dot)de> writes:
>>> Out of buffer error - Time to abort
>>
>> If this is 7.3.something, update to 7.3.4.
> I suspect that is an pgadmin III related problem,
> not a postgres problem.
No, it's definitely a backend failure. I think this CVS entry is
probably relevant:
2003-03-23 16:55 tgl
* src/backend/access/index/indexam.c (REL7_3_STABLE): Band-aid
patch for Shraibman's 'out of free buffers' bug: disable the
keys_are_unique optimization introduced in 7.3. A better fix
will
appear in 7.4, but I think back-patching it is too risky for the
stable branch.
but if Christian is running something other than 7.3-7.3.2 then we need
another theory.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
From | Date | Subject | |
---|---|---|---|
Next Message | jose | 2003-11-10 10:32:16 | CREATE DATABASE |
Previous Message | Tom Lane | 2003-11-10 01:32:53 | Re: pg_shadow dump annoying problem |