Skip site navigation (1) Skip section navigation (2)

Re: WAL archiving

From: Vishal Arora <aroravishal22(at)hotmail(dot)com>
To: Shilpa Sudhakar <ssudhakar(at)internode(dot)com(dot)au>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: WAL archiving
Date: 2008-02-25 04:06:23
Message-ID: BLU110-W214974F4F44B49930A40B0A9180@phx.gbl (view raw or flat)
Thread:
Lists: pgsql-admin
You can have a warm standby system in place. Pls check this link - http://archives.postgresql.org/sydpug/2006-10/msg00001.php 
 



> Date: Mon, 25 Feb 2008 09:54:34 +1030> From: ssudhakar(at)internode(dot)com(dot)au> To: aroravishal22(at)hotmail(dot)com> CC: pgsql-admin(at)postgresql(dot)org> Subject: Re: [ADMIN] WAL archiving> > Shilpa Sudhakar wrote:> > Hi Vishal,> >> > Below is the setup in the postgresql.conf file> >> > fsync = true # turns forced synchronization on or off> > wal_sync_method = fsync # the default varies across platforms:> > #wal_buffers = 8 # min 4, 8KB each> > #commit_delay = 0 # range 0-100000, in microseconds> > #commit_siblings = 5 # range 1-1000> >> > # - Checkpoints -> >> > checkpoint_segments = 3 # in logfile segments, min 1, 16MB each> > checkpoint_timeout = 300 # range 30-3600, in seconds> > checkpoint_warning = 30 # 0 is off, in seconds> >> > # - Archiving -> >> > archive_command = 'cp -i %p /usr/local/var/pgsql/data/wal_log/%f'> > # command to use to archive a logfile segment> >> > Since this is the test system i've put the wal_log folder in the data > > folder itself. But, later on i'll be moving this to a different disk.> >> > We have thousands and thousands of records that get inserted and > > updated so the wal logs would be increasing in a large rate. I was > > thinking if i want to delete the wal logs after a period of time, do i > > take a base backup again and then delete those old files?> >> > Thanks and Regards,> > Shilpa> >> >> > Vishal Arora wrote:> >>> >> Hi Shilpa,> >> > >> You need not take base backup again and again. You have WAL > >> Archiveing in place, that is enough to restore the database. BTW, > >> what archiving command are you using for WAL Archiving in you > >> postgresql.conf.> >>> >> - Vishal> >>> >> ------------------------------------------------------------------------> >>> >> > Date: Fri, 22 Feb 2008 09:53:25 +1030> >> > From: ssudhakar(at)internode(dot)com(dot)au> >> > To: pgsql-admin(at)postgresql(dot)org> >> > Subject: [ADMIN] WAL archiving> >> >> >> > Hi All,> >> >> >> > I am new to postgres and have been slowly learning the concepts.> >> >> >> > Regarding WAL archiving, we first take a base backup and then save all> >> > the wal logs for PITR.> >> >> >> > Both the base backup and wal logs are stored in another disk.> >> >> >> > Since the wal logs keep increasing, do we take the base backup > >> every now> >> > and then so that we can delete the old log files?> >> > How often do we take a base filesystem backup keeping in mind that our> >> > systems are 24 x 7.> >> >> >> > Any suggestions are appreciated.> >> >> >> > Thanks and Regards,> >> > Shilpa> >> >> >> >> >> > ---------------------------(end of > >> broadcast)---------------------------> >> > TIP 9: In versions below 8.0, the planner will ignore your desire to> >> > choose an index scan if your joining column's datatypes do not> >> > match> >>> >>> >> ------------------------------------------------------------------------> >> It's about getting married. Click here! Try it! > >> <http://ss1.richmedia.in/recurl.asp?pid=201>> >> >> > > ---------------------------(end of broadcast)---------------------------> TIP 7: You can help support the PostgreSQL project by donating at> > http://www.postgresql.org/about/donate
_________________________________________________________________
Post ads for free - to sell, rent or even buy.www.yello.in
http://ss1.richmedia.in/recurl.asp?pid=186

In response to

Responses

pgsql-admin by date

Next:From: Shilpa SudhakarDate: 2008-02-25 04:57:09
Subject: Re: WAL archiving
Previous:From: Phillip SmithDate: 2008-02-25 03:20:34
Subject: Backup to Tape Incomplete

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group