Re: Postmaster processes running out of control? - Mailing list pgsql-general

From Andrew Bartley
Subject Re: Postmaster processes running out of control?
Date
Msg-id 004501c1d167$601b19b0$3200a8c0@abartleypc
Whole thread Raw
In response to Re: Postmaster processes running out of control?  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: Postmaster processes running out of control?  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-general by date:

Previous
From: James F.Hranicky
Date:
Subject: Re: Storing Credit Card Info?
Next
From: Tom Lane
Date:
Subject: Re: Postmaster processes running out of control?