by Truncating the serverlog do you mean the data_log (as in my case)
log file of the postgresql sever ?. If thats the file you truncated
than i think its not a good habit..since you might need it at some
point of time for some debugging purpose in production.
You could use something like assuming
Well, a vacuum on the entire DB seemed to have cleaned things up.
No other user was logged into the server, and I certainly did not send
the signal.
I did clean up the serverlog file by truncating it ( > serverlog)
while the DB was running, I don't think it liked that since it crashed
the DB. I
Don Drake <[EMAIL PROTECTED]> writes:
> My server is crashing on a delete statement.
> Here's the error message in the log file:
> LOG: 0: received fast shutdown request
> LOCATION: pmdie, postmaster.c:1736
That says that something sent the postmaster a SIGINT signal.
I think it's highly un
My server is crashing on a delete statement.
Here's the error message in the log file:
LOCATION: ShutdownXLOG, xlog.c:3090
LOG: 0: database system is shut down
LOCATION: ShutdownXLOG, xlog.c:3104
LOG: 0: database system was shut down at 2005-04-10 21:54:34 CDT
LOCATION: StartupXLOG,
