| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Sergei Shelukhin" <realgeek(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: truncate transaction log |
| Date: | 2007-08-07 15:47:42 |
| Message-ID: | dcc563d10708070847t5aab9713t65c79dacb1d9a848@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 8/5/07, Sergei Shelukhin <realgeek(at)gmail(dot)com> wrote:
> Hi.
>
> Is there any way to truncate WAL log in postgres?
> We want to use full-backup strategy where we stop the server and copy
> the data directory, however WAL log is taking dozens gigabytes of
> spaces.
> Is there any way to remove it while keeping the database operational/
> restore-able by copying it back?
This sounds unusually high. What non-default settings are there in
your postgresql.conf file? Are you using PITR or something like that?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vivek Khera | 2007-08-07 15:54:29 | Re: How do I connect postgres table structures and view structures to an existing svn repository? |
| Previous Message | Steve Atkins | 2007-08-07 15:40:47 | Re: finding out vacuum completion %, and vacuum VS vacuum full |