| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rasmus Mohr <rmo(at)Netpointers(dot)com> |
| Cc: | "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Troubles with WAL and pg_control |
| Date: | 2002-04-24 14:53:39 |
| Message-ID: | 12290.1019660019@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Rasmus Mohr <rmo(at)Netpointers(dot)com> writes:
> Hi, we have serious problem with our postgresql db.
> A staling query were killed and all the WAL files were deleted.
Just for the benefit of onlookers: that was a really BAD idea.
The pg_xlog and pg_clog files are not optional; you *will* regret it
if you decide to delete 'em.
BTW, if you want to kill a runaway query, it's usually sufficient
to do "kill -INT" on the specific backend doing the query. This
executes a query-cancel, which should stop the query fairly quickly
without any damage to the rest of the system.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Denny-Schierz | 2002-04-24 15:58:05 | is it a bug? |
| Previous Message | Rasmus Mohr | 2002-04-24 11:56:19 | Re: Troubles with WAL and pg_control |