| From: | Sergei Shelukhin <realgeek(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: truncate transaction log |
| Date: | 2007-08-07 18:42:13 |
| Message-ID: | 1186512133.011190.171480@57g2000hsv.googlegroups.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Aug 7, 9:57 pm, si(dot)(dot)(dot)(at)2ndquadrant(dot)com ("Simon Riggs") wrote:
> On Sun, 2007-08-05 at 03:45 -0700, Sergei Shelukhin wrote:
> > 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?
>
> Reduce the setting of checkpoint_segments to something more realistic.
>
Hmm. Reduced to 60, during the db conversion from MySQL Postgres used
to complain about this setting so I increased it to the sky. Thanks :)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Shelukhin | 2007-08-07 18:47:07 | Re: finding out vacuum completion %, and vacuum VS vacuum full |
| Previous Message | Andrej Ricnik-Bay | 2007-08-07 18:27:13 | Re: [SQL] Restricting columns by users |