..
> Could you give a bit more context about when exactly that error is
> happening?
> It would also be helpful if you could set log_error_verbosity =
> 'verbose'; in the config file and report back with the complete error
> message, including line numbers.
>
>
I try to restart DB and seems get this situation:
===
2012-11-18 18:30:25 EET pid:93744 LOG: received SIGHUP, reloading
configuration files
2012-11-18 18:30:25 EET pid:93744 LOG: 00000: parameter
"log_error_verbosity" changed to "verbose"
2012-11-18 18:30:25 EET pid:93744 LOCATION: ProcessConfigFile,
guc-file.l:318
2012-11-18 18:36:45 EET pid:93744 LOG: 00000: received fast shutdown
request
2012-11-18 18:36:45 EET pid:93744 LOCATION: pmdie, postmaster.c:2187
2012-11-18 18:36:45 EET pid:93744 LOG: 00000: aborting any active
transactions
2012-11-18 18:36:45 EET pid:93744 LOCATION: pmdie, postmaster.c:2211
2012-11-18 18:36:45 EET pid:93749 LOG: 00000: autovacuum launcher
shutting down
2012-11-18 18:36:45 EET pid:93749 LOCATION: AutoVacLauncherMain,
autovacuum.c:767
2012-11-18 18:36:45 EET pid:93746 LOG: 00000: shutting down
2012-11-18 18:36:45 EET pid:93746 LOCATION: ShutdownXLOG, xlog.c:7560
2012-11-18 18:36:45 EET pid:93746 LOG: 00000: database system is shut
down
2012-11-18 18:36:45 EET pid:93746 LOCATION: ShutdownXLOG, xlog.c:7582
2012-11-18 18:36:46 EET pid:95528 FATAL: XX000: poll() failed: Invalid
argument
2012-11-18 18:36:46 EET pid:95528 LOCATION: WaitLatchOrSocket,
pg_latch.c:296
===
After several minutes the rc.d script said:
pg_ctl: could not start server
Examine the log output.
Then I did:
killall -2 postgres
killall -3 postgres
And this remains procesess:
95527 pgsql 1 52 0 2159M 82400K pipewr 10 0:00 0.00%
postgres
95540 pgsql 1 20 0 2163M 83432K pipewr 0 0:00 0.00%
postgres
I can stop only via killall -9 :(
--
Regards
System and web developer.
<http://amkmobile.com>