X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id D98289DCD80 for ; Tue, 28 Mar 2006 09:41:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 49456-01 for ; Tue, 28 Mar 2006 09:41:09 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.191]) by postgresql.org (Postfix) with ESMTP id DED339DCD87 for ; Tue, 28 Mar 2006 09:41:03 -0400 (AST) Received: by nproxy.gmail.com with SMTP id k27so1088508nfc for ; Tue, 28 Mar 2006 05:41:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=hYknx/wNZOHq/6HWuP6eDLk6THPsfjL/G17RHxG9MotLBbfdnorWsWEC8aiMm+CYoDTOgYbvoFi6MrwdrnMwy2aZfxlA4ZDAefucMLkprHGt6okZE557msQ+LeAj3M+UN26XjgIp6GywJ8Cn8dhO5jPzi6IGddWzHs+rroCRDUE= Received: by 10.49.91.1 with SMTP id t1mr500752nfl; Tue, 28 Mar 2006 05:41:07 -0800 (PST) Received: by 10.49.27.1 with HTTP; Tue, 28 Mar 2006 05:41:07 -0800 (PST) Message-ID: Date: Tue, 28 Mar 2006 19:11:07 +0530 From: "Rajesh Kumar Mallah" To: pgsql-admin@postgresql.org Subject: Setting up of PITR system. Cc: mallah@trade-india.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_15421_10954525.1143553267460" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.946 required=5 tests=[HTML_10_20=0.945, HTML_MESSAGE=0.001] X-Spam-Score: 0.946 X-Spam-Level: X-Archive-Number: 200603/304 X-Sequence-Number: 21061 ------=_Part_15421_10954525.1143553267460 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, We are trying to setup PITR system based on documentation http://www.postgresql.org/docs/8.1/interactive/backup-online.html We have 3 questions regarding 1. Selection of archived WAL records that can be safely removed. 2. Knowing the relevant WAL record just after pg_stop_backup() 3. Recommended tool for taking file system level backup. Elaboration: we want to remove archived WAL log files which are no longer needed so that the size of wal_archive folder is under control. The DOCs say that filenames numerically less than the WAL record that pg_stop_backup() suggests can be removed. Will an alphabetical sorting be different from numerically sorted filename ? Sorting numerically is not easy as the filenames look like HE= X numbers ut they are are so huge that they cant be stored in normal integers (32bits). Q2. We are attempting to automate the process of taking base backup and removal of the unneeded WAL files. Is there any reliable way of knowing the WA= L file X from inside the shell script , such that files prior to X can be removed ? from a shell script we issue pg_stop_backup() by psql -c , it returns something which does not looks like a WAL file. Regds Rajesh Kumar Mallah. ------=_Part_15421_10954525.1143553267460 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,

We are trying to setup PITR system based on documentation
http://www.postgresql.org/docs/8.1/interactive/backup-online.html
We have 3 questions regarding

1. Selection of archived WAL records that can be safely removed.
2. Knowing the relevant WAL record just after pg_stop_backup()
3. Recommended tool for taking file system level backup.

Elaboration:

we want to remove archived WAL log files which are no longer needed
so that the size of wal_archive folder is under control.

The DOCs say that filenames numerically less than the WAL record that pg_st= op_backup()
suggests can be removed. Will an alphabetical sorting be different from num= erically sorted
filename ?    Sorting numerically is not easy as the filenames lo= ok like HEX numbers
ut they are are so huge that they cant be stored in normal integers (32bits= ).


Q2. We are attempting to automate the process of taking base backup and rem= oval
     of the unneeded WAL files. Is there any reliable w= ay of knowing the WAL file X from
     inside the shell script , such that files prior to= X can be removed ?

from a shell script we issue pg_stop_backup() by psql -c , it returns somet= hing
   which does not looks like a WAL file.

Regds
Rajesh Kumar Mallah.
  
------=_Part_15421_10954525.1143553267460--