Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 6C05E2E0101 for ; Mon, 25 Feb 2008 00:06:29 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 85628-10 for ; Mon, 25 Feb 2008 00:06:24 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from blu139-omc1-s8.blu139.hotmail.com (blu139-omc1-s8.blu139.hotmail.com [65.55.175.148]) by postgresql.org (Postfix) with ESMTP id B9DA42E0054 for ; Mon, 25 Feb 2008 00:06:24 -0400 (AST) Received: from BLU110-W21 ([65.55.162.182]) by blu139-omc1-s8.blu139.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 24 Feb 2008 20:06:23 -0800 Message-ID: Content-Type: multipart/alternative; boundary="_35212c52-56a1-4b61-a083-0ba0edf2eb99_" X-Originating-IP: [59.160.193.34] From: Vishal Arora To: Shilpa Sudhakar CC: Subject: Re: WAL archiving Date: Mon, 25 Feb 2008 09:36:23 +0530 Importance: Normal In-Reply-To: <47C1FCB2.3070401@internode.com.au> References: <47BE07ED.1070802@internode.com.au> <47C1FC77.6070507@internode.com.au> <47C1FCB2.3070401@internode.com.au> MIME-Version: 1.0 X-OriginalArrivalTime: 25 Feb 2008 04:06:23.0871 (UTC) FILETIME=[C90EB0F0:01C87763] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.002 tagged_above=0 required=5 tests=AWL=0.001, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200802/304 X-Sequence-Number: 28378 --_35212c52-56a1-4b61-a083-0ba0edf2eb99_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable You can have a warm standby system in place. Pls check this link - http://a= rchives.postgresql.org/sydpug/2006-10/msg00001.php=20 =20 > 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 =3D true # turns force= d synchronization on or off> > wal_sync_method =3D fsync # the default vari= es across platforms:> > #wal_buffers =3D 8 # min 4, 8KB each> > #commit_del= ay =3D 0 # range 0-100000, in microseconds> > #commit_siblings =3D 5 # rang= e 1-1000> >> > # - Checkpoints -> >> > checkpoint_segments =3D 3 # in logfi= le segments, min 1, 16MB each> > checkpoint_timeout =3D 300 # range 30-3600= , in seconds> > checkpoint_warning =3D 30 # 0 is off, in seconds> >> > # - = Archiving -> >> > archive_command =3D 'cp -i %p /usr/local/var/pgsql/data/w= al_log/%f'> > # command to use to archive a logfile segment> >> > Since thi= s is the test system i've put the wal_log folder in the data > > folder its= elf. But, later on i'll be moving this to a different disk.> >> > We have t= housands 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 u= sing for WAL Archiving in you > >> postgresql.conf.> >>> >> - Vishal> >>> >= > ------------------------------------------------------------------------>= >>> >> > Date: Fri, 22 Feb 2008 09:53:25 +1030> >> > From: ssudhakar@inter= node.com.au> >> > To: pgsql-admin@postgresql.org> >> > Subject: [ADMIN] WAL= archiving> >> >> >> > Hi All,> >> >> >> > I am new to postgres and have be= en slowly learning the concepts.> >> >> >> > Regarding WAL archiving, we fi= rst 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 > >> e= very 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> >> > sy= stems are 24 x 7.> >> >> >> > Any suggestions are appreciated.> >> >> >> > = Thanks and Regards,> >> > Shilpa> >> >> >> >> >> > ------------------------= ---(end of > >> broadcast)---------------------------> >> > TIP 9: In versi= ons below 8.0, the planner will ignore your desire to> >> > choose an index= scan if your joining column's datatypes do not> >> > match> >>> >>> >> ---= ---------------------------------------------------------------------> >> I= t's about getting married. Click here! Try it! > >> > >> >> > > ---------------------------(end of broad= cast)---------------------------> TIP 7: You can help support the PostgreSQ= L 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=3D186= --_35212c52-56a1-4b61-a083-0ba0edf2eb99_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
You can have a warm standby system in place. = Pls check this link - http://archives.postgresql.org/sydpug/2006-10/msg00001.ph= p 



 


> Date: Mon, 25 Feb 2008 09:54:34 +1030
> From: ssudhakar@internod= e.com.au
> To: aroravishal22@hotmail.com
> CC: pgsql-admin@post= gresql.org
> Subject: Re: [ADMIN] WAL archiving
>
> Shil= pa Sudhakar wrote:
> > Hi Vishal,
> >
> > Below = is the setup in the postgresql.conf file
> >
> > fsync = =3D true # turns forced synchronization on or off
> > wal_sync_met= hod =3D fsync # the default varies across platforms:
> > #wal_buff= ers =3D 8 # min 4, 8KB each
> > #commit_delay =3D 0 # range 0-1000= 00, in microseconds
> > #commit_siblings =3D 5 # range 1-1000
&= gt; >
> > # - Checkpoints -
> >
> > checkpoin= t_segments =3D 3 # in logfile segments, min 1, 16MB each
> > check= point_timeout =3D 300 # range 30-3600, in seconds
> > checkpoint_w= arning =3D 30 # 0 is off, in seconds
> >
> > # - Archivin= g -
> >
> > archive_command =3D 'cp -i %p /usr/local/var/= pgsql/data/wal_log/%f'
> > # command to use to archive a logfile s= egment
> >
> > 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 thou= sands and thousands of records that get inserted and
> > updated = so the wal logs would be increasing in a large rate. I was
> > th= inking if i want to delete the wal logs after a period of time, do i
&g= t; > take a base backup again and then delete those old files?
> &= gt;
> > Thanks and Regards,
> > Shilpa
> >
&g= t; >
> > 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 co= mmand are you using for WAL Archiving in you
> >> postgresql.c= onf.
> >>
> >> - Vishal
> >>
> &g= t;> --------------------------------------------------------------------= ----
> >>
> >> > Date: Fri, 22 Feb 2008 09:53:25= +1030
> >> > From: ssudhakar@internode.com.au
> >&= gt; > To: pgsql-admin@postgresql.org
> >> > Subject: [ADM= IN] WAL archiving
> >> >
> >> > Hi All,
&g= t; >> >
> >> > I am new to postgres and have been s= lowly learning the concepts.
> >> >
> >> > Re= garding WAL archiving, we first take a base backup and then save all
>= ; >> > the wal logs for PITR.
> >> >
> >&g= t; > Both the base backup and wal logs are stored in another disk.
&g= t; >> >
> >> > 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?
> >> > H= ow often do we take a base filesystem backup keeping in mind that our
&g= t; >> > systems are 24 x 7.
> >> >
> >>= > Any suggestions are appreciated.
> >> >
> >&g= t; > Thanks and Regards,
> >> > Shilpa
> >> &= gt;
> >> >
> >> > ---------------------------= (end of
> >> broadcast)---------------------------
> >= ;> > TIP 9: In versions below 8.0, the planner will ignore your desir= e to
> >> > choose an index scan if your joining column's da= tatypes do not
> >> > match
> >>
> >>= ;
> >> --------------------------------------------------------= ----------------
> >> It's about getting married. Click here! T= ry it!
> >> <http://ss1.richmedia.in/recurl.asp?pid=3D201&g= t;
> >
> >
>
>
> --------------------= -------(end of broadcast)---------------------------
> TIP 7: You can= help support the PostgreSQL project by donating at
>
> http:/= /www.postgresql.org/about/donate



Post free auto ads on Y= ello Classifieds now! Try it now! = --_35212c52-56a1-4b61-a083-0ba0edf2eb99_--