[GENERAL] Ouch!

Running 8.1.3 on FreeBSD 6.0 server and got the following (I'm most interested in the "PANIC" entry): 2007-02-06 17:15:11 CST LOG: archived transaction log file "000104A30025" 2007-02-06 17:15:27 CST LOG: archived transaction log file "000104A30026" 2007-02-06 17:15

[GENERAL] pg_controldata output documentation

I'd like to calculate the name of the WAL file associated with the latest checkpoint using the output from pg_controldata: Latest checkpoint location: 74/FD9827C0 Prior checkpoint location:74/FD6FCDC8 Latest checkpoint's REDO location:74/FD87DDF8 Latest checkpoint's UND

[GENERAL] SET statement_timeout

We run VACUUM ANALYZE as a cron job on PostgreSQL v8.1.3 on an Opteron box running FreeBSD 6.0-RELEASE #10. We set statement_timeout to 720 in postgresql.conf. Since this task often takes longer than two hours we encounter the following messages in our log files: 2006-11-30 00:03:31 CST ER

[GENERAL] pg_controldata output documentation

Is there any documentation on the output from pg_controldata? Most of it seems intuitive but I would like something definitive on the following lines: Latest checkpoint location: 2F9/B38DE758 Prior checkpoint location:2F9/A3F688F8 Latest checkpoint's REDO location:2F9/

Re: [GENERAL] Unable to restart postgres - database system was

. Nothing was done to the database other than a shutdown and restart. The age of the pg_control file coincided with the the time we stopped Postgres. Tom Lane wrote: andy rost <[EMAIL PROTECTED]> writes: We stopped postgres using kill -TERM. When we tried to restart the engine, it wo

[GENERAL] Unable to restart postgres - database system was interrupted

Running Postgres version 8.1.3 on Opteron box running FreeBSD 6.0-RELEASE #10. We stopped postgres using kill -TERM. When we tried to restart the engine, it would not recover. The logs stated the following: 2006-12-04 10:18:39 CST LOG: archived transaction log file "0001006900

[GENERAL] URGENT - startup process (PID 29541) was terminated by signal 6

Our Opteron DB server had a problem with its RAID controller requiring an immediate shutdown of our Postgres server (8.1.3 on FreeBSD 6.0 release number 10). We used kill -QUIT on the postmaster PID. After repairing and rebooting the server we tried to start Postgres and get the following: 2

[GENERAL] pgpool on Opteron server running FreeBSD 6.0

I'm running postgres 8.1.3 on a 2-CPU dual-core Opteron server with 8-Gigs of RAM. The server's operating system is FreeBSD 6.0. We migrated our client applications from Informix and went through all of the standard steps to resolve differences between the two databases packages. However, there