From: | "Andrew Bartley" <abartley(at)evolvosystems(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postmaster processes running out of control? |
Date: | 2002-03-22 06:04:06 |
Message-ID: | 004501c1d167$601b19b0$3200a8c0@abartleypc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2002-03-22 16:44:28 [383] DEBUG: SIInsertDataEntry: table is 70% full,
signaling postmaster
2002-03-22 16:44:28 [383] NOTICE: RegisterSharedInvalid: SI buffer
overflow
2002-03-22 16:44:28 [315] NOTICE: InvalidateSharedInvalid: cache state
reset
2002-03-22 16:44:28 [279] NOTICE: InvalidateSharedInvalid: cache state
reset
2002-03-22 16:44:28 [278] NOTICE: InvalidateSharedInvalid: cache state
reset
2002-03-22 16:44:28 [277] NOTICE: InvalidateSharedInvalid: cache state
reset
2002-03-22 16:44:28 [276] NOTICE: InvalidateSharedInvalid: cache state
reset
This is happening once a rather large batch process commits ie a PLPGSQL
function from within cron.
I have had a good look through groups and most of the time it seems to be
related to a vacuum.
In this circumstance it is causing a peer process job that useses
persistant connections to receive a SIGPIPE signal.
Can some one please advise us can we stop the table filling? Or can we stop
the SIGPIPE?
Thanks
Andrew Bartley
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-03-22 06:20:19 | Re: Postmaster processes running out of control? |
Previous Message | James F.Hranicky | 2002-03-22 04:40:20 | Re: Storing Credit Card Info? |