On 10/19/2012 04:40 PM, raghu ram wrote: > Hi All, > > We have configured Streaming Replication b/w Primary and Standby server > and Pgpool-II load balancing module diverting > SELECT statements to Standby server. As per our observations, Standby > server crashed during peak hours on today and error message as follows > 2012-10-19 12:26:46 IST [1338]: [18-1] user=,db= LOG: server process > (PID 15565) was terminated by signal 10 > > 2012-10-19 12:26:46 IST [1338]: [19-1] user=,db= LOG: terminating any > other active server processes That's odd. SIGUSR1 (signal 10) shouldn't terminate PostgreSQL. Was the server intentionally sent SIGUSR1 by an admin? Do you know what triggered the signal? Are you running any procedural languages other than PL/PgSQL, or any custom C extensions? Anything that might have unwittingly cleared the signal handler for SIGUSR1? -- Craig Ringer -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
