Hello,

I don't know whether this really is a bug or is just
something I don't know how to configure in the db.

I wrote a PL/SQL stored procedure which performs a
huge transaction cca. 2 milion record insert.

The procedure performs transacting and atfer a while
error is thrwn: out od shared memory.

Up to this point everything is OK, even error is OK since I
have very modest shared memory segment configured in .ini
file.

But here comes something I think it is a bug. Shared memory can not
be recovered from this point on. Everthing operation I try to
perform on db says: out of shared memory. And the only option
I have is to shutdown postmaster and start it again.

We are testing postreSQL to run it in production, but this is
unfortunately untolerable for us.

This strange behaviour is with version 8.0.0 beta1

With regards, Rikardo

P.S.: If this is not a bug, please tell me how to correct it.


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

Rikardo Tinauer <rikardo (AT) ebaeu (DOT) com> writes:
Hmm. We've fixed a number of leakage problems since beta1, but I don't
recall any that would have quite that symptom. Could you verify whether
it still occurs on beta2 (or better yet, a recent daily snapshot)?
If so, please send in a complete test case.

[ raised eyebrow... ] Please tell me you're not seriously thinking of
running production on a beta release.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster