Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YWkH4-0003ls-OS for pgsql-admin@arkaria.postgresql.org; Sat, 14 Mar 2015 11:30:34 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YWkH4-0005xk-1Q for pgsql-admin@arkaria.postgresql.org; Sat, 14 Mar 2015 11:30:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YWkH3-0005xc-Am for pgsql-admin@postgresql.org; Sat, 14 Mar 2015 11:30:33 +0000 Received: from mail-wg0-x229.google.com ([2a00:1450:400c:c00::229]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YWkH0-00032i-MA for pgsql-admin@postgresql.org; Sat, 14 Mar 2015 11:30:32 +0000 Received: by wgra20 with SMTP id a20so6429604wgr.3 for ; Sat, 14 Mar 2015 04:30:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:reply-to:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; bh=KLSmRi1ZXrZFhHGTKdNPEcvj9tLW0TsJfxHYly2ey2A=; b=dFXL7y0Gt095ZZxClbmeKufdLqdumy3vrUVZaV9+Q1bYxo42vv1B8nNjnPtnW16SrR bNlUmbgo1oLWJzQdDHvYm9iW454N8mJzBb+F2CKuIwnIf16pvuEh8UfTTCympbbgnf8q PUVxdNYui2h0bW/csn1u2racibtSs2WLlgxFIQJXcOWZ5qufo8XVLOTtc2pPBeo/uY+6 +p9IACJnmrmTjeJ717cAJkS7lpkJo4K6vgZxYSQQoOdXzJqH5swd62KDiijnh5lJemSQ r54L5wOQ5qKN833U5J2H3PG/g70xhoI75U9mcCVNYQ5hnsq6RJWtuRETK86cYSCAzpoW 7mcA== X-Received: by 10.194.57.206 with SMTP id k14mr107040644wjq.1.1426332629385; Sat, 14 Mar 2015 04:30:29 -0700 (PDT) Received: from enterprisedb01 (84.125.177.156.dyn.user.ono.com. [84.125.177.156]) by mx.google.com with ESMTPSA id e2sm6622481wjy.46.2015.03.14.04.30.28 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Mar 2015 04:30:28 -0700 (PDT) Message-ID: <1426332627.3775.4.camel@gmail.com> Subject: Re: PITR compatible backup with exclusion From: jaime soler Reply-To: jaime.soler@gmail.com To: Thomas Kellerer Cc: pgsql-admin@postgresql.org Date: Sat, 14 Mar 2015 12:30:27 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.10-0ubuntu1~14.10.1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.7 (--) 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 El mar, 27-01-2015 a las 08:36 +0100, Thomas Kellerer escribió: > Martin Bruset Solberg schrieb am 26.01.2015 um 13:17: > > I am faced with a scenario of backing up a database with one large > > (partitioned) table, and several smaller tables. The large table is > > so big that backing it up is proving problematic both in terms of > > storage and time spent backing up and restoring. The backup of the > > table itself is also reduntant, as the table data can be recreated by > > importing from the source files. This data is not mission critical > > for the application, so a speedy recovery is not urgent. The data > > from the smaller tables, however, is critical. The combined size of > > the rest of the database is not a problem neither in terms of storage > > or backup/restore speed, so a logical backup excluding the large > > table/schema works fine. But logical backup is not sufficiant, as I > > need to be able to do PITR in case of disaster. > > > > So my question is, what are my options when I want to make a PITR > > compatible backup, and need to exclude a table/schema/tablespace of > > the database? Any suggestions welcome... > > > What if you change that big table to UNLOGGED? > As unlogged tables don't generate WAL they don't contribute to the PITR "restore time" > (and they won't be restored if you have to do a PITR!) However, they are not crash-safe: an unlogged table is automatically truncated after a crash or unclean shutdown. > > It will be included in the necessary base backup though if I'm not mistaken. > > Thomas > > > -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin