| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: recover corrupt DB? |
| Date: | 2009-05-05 19:53:30 |
| Message-ID: | 20090505195330.GU4476@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dan Armbrust escribió:
> My particular disk-full condition was on ext2. Nothing exotic. Also,
> the process that filled the disk was postgres - if that makes any
> difference - I had left a debug level turned up in the postgres config
> file, and it was logging every single db query. Since it wasn't set
> up to remove old log files - it filled the disk.
>
> Nothing else unusual occurred that I'm aware of - things went weird
> for the lab tester, he cleared some space, rebooted the system, and
> postgres didn't come back online.
Did "cleared some space" include the pg_xlog directory or something in
the vicinity?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | CM J | 2009-05-06 04:56:19 | Postgres: Transaction Connections |
| Previous Message | Jeff Davis | 2009-05-05 18:18:18 | Re: PGSQL-to-MYSQL Migration: Error in a 'simple' inner join query |