pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-admin@postgresql.org, Steve Holdoway <steve.holdoway@firetrust.com>
Subject: Re: Backup of live database
Date: Wed, 16 Jan 2008 10:50:31 -0500
Message-ID: <24080.1200498631@sss.pgh.pa.us> (raw)
In-Reply-To: <200801161639.12326.peter_e@gmx.net>
References: <5a9699850801152257g6ee9513i6c4fc88a5f20a785@mail.gmail.com>
	<20080116233030.c1adbcb1.steve.holdoway@firetrust.com>
	<23635.1200496752@sss.pgh.pa.us>
	<200801161639.12326.peter_e@gmx.net>

Peter Eisentraut <peter_e@gmx.net> writes:
> Am Mittwoch, 16. Januar 2008 schrieb Tom Lane:
>> (Thinks for a bit...) Actually I guess there's one extra assumption in
>> there, which is that tar must issue its reads in multiples of our page
>> size.  But that doesn't seem like much of a stretch.

> There is something about that here: 
> http://www.gnu.org/software/tar/manual/html_node/tar_149.html#SEC149

AFAICT that's talking about the I/O chunk size *on the archive file*.
It doesn't say anything specific about the chunk size on the file side.

			regards, tom lane



view thread (18+ messages)  latest in thread

Message-ID: <24080.1200498631@sss.pgh.pa.us>
Permalink:  ../24080.1200498631@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24080.1200498631@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, peter_e@gmx.net, steve.holdoway@firetrust.com
  Subject: Re: Backup of live database
  In-Reply-To: <24080.1200498631@sss.pgh.pa.us>

* 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