Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCXCe-0004a7-6z for pgsql-admin@arkaria.postgresql.org; Thu, 22 Aug 2013 15:53:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VCXCd-0002Rs-Ll for pgsql-admin@arkaria.postgresql.org; Thu, 22 Aug 2013 15:53:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VCXCb-0002Px-Sb for pgsql-admin@postgresql.org; Thu, 22 Aug 2013 15:53:37 +0000 Received: from nm18-vm8.bullet.mail.sg3.yahoo.com ([106.10.149.103]) by magus.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VCXCV-0002cE-8E for pgsql-admin@postgresql.org; Thu, 22 Aug 2013 15:53:37 +0000 Received: from [106.10.166.125] by nm18.bullet.mail.sg3.yahoo.com with NNFMP; 22 Aug 2013 15:53:29 -0000 Received: from [106.10.151.203] by tm14.bullet.mail.sg3.yahoo.com with NNFMP; 22 Aug 2013 15:53:29 -0000 Received: from [127.0.0.1] by omp1015.mail.sg3.yahoo.com with NNFMP; 22 Aug 2013 15:53:29 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 72810.27638.bm@omp1015.mail.sg3.yahoo.com Received: (qmail 58830 invoked by uid 60001); 22 Aug 2013 15:53:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.hk; s=s1024; t=1377186808; bh=e9rcW68TS6+bcLEjc9ptnM5H2Ye8z4v4IvfMH2sK2io=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=6LWb8uxfI/5WISEJP1VsFvBzCd43tsWjqZ+fS7c2YzlxT9h0ckoGSfCiMIffRH/FDmKzA/0Lahl3UiGZzrrzhBHszNL9jgdpIFAerIsSbcoIGyV4T+1G9Lw/ZO0ce/Z/TdrK3FjOdY0HP0MTXluIEBKYdFmLjgwdC3TFWcOK6PY= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.hk; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=0I7uujTN9vV64HVa2LR2j0dYErfnYDa7IVyGx6vcE4++HS4kVL2ovTTXBPRFB+6siqiCiRb93e1R6V5ZatxLHHo9GPoHKfeKU21VJIQDi9BPulbmjoFdk6ZL2NaEBD6lmXObRT3b3Q846dxzc1qdklx8UxksFMNfz5kLTQzy6LQ=; X-YMail-OSG: PLaCNR4VM1nIdWRCVnloBhmMp3yQXlcKoxxl5EnbR8nMG8_ BNNvuC09QDtY858EdC3UxTaBuy4Mc1ozKp381mnRBNqPYaBzHElQ3lolK6Ef M3SICAkLcwMogU4gT4c9cJYvn7WBUFDwG7gvruvFalC4fu8koqT6Ywlrrbd0 E0nciQj4Wr4wIicPCJgbcDVdPyB4l3RwgzjVC0yLHsdPhe8sRioZuaEPUchz nBYM44KP_42ZX0XMAeOUabQua4IPGPXJO7oeBGhvYxFjefBiECcYSxUWhsEK k.dWMJtVYX.1HQv6kGVF_WkGjWpStCtLJ7F_9XgLn1zYucM5lviFutMKzjhM 9H8G.L7MslefxNKeC0NxbWeFaklgTn1Vmb_W75mGdEvQPJTXXNDjDr_0AcNV 7ZpxTr2VZg8G6ka4QXfgTPbDtlmBdKGy.DYnhsr_VVrlemtODcgiV7uM.HZP GWqIS1XrLTnFT_ry_2guJ9NIZOK71J_DdJCHrBYuWFrysklwu1I8CNBZC3LM Y4NYosKvWpfquJu3VQ9d4w1aB5.0F75thoLoSPgO4cblI84NP3MOnwWc- Received: from [61.15.240.116] by web193505.mail.sg3.yahoo.com via HTTP; Thu, 22 Aug 2013 23:53:28 SGT X-Rocket-MIMEInfo: 002.001, SGkgYWxsLAoKSSBoYXZlIHNvbWUgcXVlc3Rpb25zIGFib3V0IGJhY2t1cCBvbiBQb3N0Z3JlU1FMOgoKMSkgcGdfZHVtcGFsbApJIGFtIHN1cmUgdGhhdCB0aGlzIGlzIGFza2VkIGluIHNvbWV3aGVyZTogd2h5IHRoZSBwZ19kdW1wYWxsIGRvZXMgbm90IHN1cHBvcnQgY3VzdG9tIG9yIHRhciBmb3JtYXQgbGlrZSBwZ19kdW1wLgpJIGhhdmUgaGVhcmQgdGhhdCB0aGUgY3VzdG9tIGZvcm1hdCBjb3VsZCBiZSBmYXN0ZXIgYW5kIG1heSBnZW5lcmF0ZSBhIHNtYWxsZXIgZHVtcCBmaWxlLgpJcyB0aGUgZmVhdHUBMAEBAQE- X-Mailer: YahooMailWebService/0.8.155.576 Message-ID: <1377186808.57546.YahooMailNeo@web193505.mail.sg3.yahoo.com> Date: Thu, 22 Aug 2013 23:53:28 +0800 (SGT) From: Patrick Dung Reply-To: Patrick Dung Subject: several questions about pg_dumpall, pg_start_backup, pg_basebackup and WAL To: "pgsql-admin@postgresql.org" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-1392289268-1982874597-1377186808=:57546" X-Pg-Spam-Score: 2.0 (++) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org ---1392289268-1982874597-1377186808=:57546 Content-Type: text/plain; charset=us-ascii Hi all, I have some questions about backup on PostgreSQL: 1) pg_dumpall I am sure that this is asked in somewhere: why the pg_dumpall does not support custom or tar format like pg_dump. I have heard that the custom format could be faster and may generate a smaller dump file. Is the feature enhancement being developed? 2) pg_start_backup in postgresql 8.4 After issuing pg_start_backup, we can take the file based backup (by tar/snapshot) on the postgresql data directory. If the use of file system snapshot is not possible. It is possible that there is file changes (added or file size changed) between the pg_start_backup and pg_stop_backup. Is the backup consistent? 3) extension of 2): If the postgresql version is 9.2 Is pg_basebackup better than pg_start_backup + file based backup + pg_stop_backup? 4) For the WAL backup in postgresql 8.4 After the archive mode is on and WAL is backup, how do I remove the old WAL files? How about newer version (for example 9.2?) Thanks and regards, Patrick ---1392289268-1982874597-1377186808=:57546 Content-Type: text/html; charset=us-ascii
Hi all,

I have some questions about backup on PostgreSQL:

1) pg_dumpall
I am sure that this is asked in somewhere: why the pg_dumpall does not support custom or tar format like pg_dump.
I have heard that the custom format could be faster and may generate a smaller dump file.
Is the feature enhancement being developed?

2) pg_start_backup in postgresql 8.4
After issuing pg_start_backup, we can take the file based backup (by tar/snapshot) on the postgresql data directory.
If the use of file system snapshot is not possible.
It is possible that there is file changes (added or file size changed) between the pg_start_backup and pg_stop_backup.
Is the backup consistent?

3) extension of 2): If the postgresql version is 9.2
Is pg_basebackup better than pg_start_backup + file based backup + pg_stop_backup?

4) For the WAL backup in postgresql 8.4
After the archive mode is on and WAL is backup, how do I remove the old WAL files?
How about newer version (for example 9.2?)

Thanks and regards,
Patrick


---1392289268-1982874597-1377186808=:57546--