| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephanie Brail <zhaanlives(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: deleted logs when I shouldn't have... |
| Date: | 2001-11-06 18:41:40 |
| Message-ID: | 17116.1005072100@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Stephanie Brail <zhaanlives(at)yahoo(dot)com> writes:
> I did something really stupid. Our server was out of
> disk space and I deleted the files in the pg_xlog
> directory (or whatever the heck it's called). Now I
> can't start Postgres. Help!
If you shut down the postmaster cleanly before you zapped pg_xlog, then
I think it will work safely to run contrib/pg_resetxlog and start the
postmaster.
If you zapped pg_xlog in a running system or after a crash, you can
still do the resetxlog, but there's no guarantee that your last few
transactions will have applied cleanly --- you may find that some or
all of the effects of "committed" xacts are missing.
> Also, how to deal with these logs, that grow and grow
> and take up space?
7.1.3 is better about that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-06 18:47:10 | Re: psql hangs when trying to access a database |
| Previous Message | Andrew Gould | 2001-11-06 18:35:06 | Re: copy command with PSQL |