pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vishal Arora <aroravishal22@hotmail.com>
To: Shilpa Sudhakar <ssudhakar@internode.com.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL archiving
Date: Mon, 25 Feb 2008 09:36:23 +0530
Message-ID: <BLU110-W214974F4F44B49930A40B0A9180@phx.gbl> (raw)
In-Reply-To: <47C1FCB2.3070401@internode.com.au>
References: <47BE07ED.1070802@internode.com.au>
	<BLU110-W165FBE7261A87F71FBB522A91D0@phx.gbl>
	<47C1FC77.6070507@internode.com.au>
	<47C1FCB2.3070401@internode.com.au>

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@internode.com.au> To: aroravishal22@hotmail.com> CC: pgsql-admin@postgresql.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@internode.com.au> >> > To: pgsql-admin@postgresql.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=

view thread (11+ messages)  latest in thread

Message-ID: <BLU110-W214974F4F44B49930A40B0A9180@phx.gbl>
Permalink:  ../BLU110-W214974F4F44B49930A40B0A9180@phx.gbl/
Also on:    postgresql.org/message-id/BLU110-W214974F4F44B49930A40B0A9180@phx.gbl

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: aroravishal22@hotmail.com, ssudhakar@internode.com.au
  Subject: Re: WAL archiving
  In-Reply-To: <BLU110-W214974F4F44B49930A40B0A9180@phx.gbl>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox