Re: Block size with pg_dump? - Mailing list pgsql-sql

From Bruce Momjian
Subject Re: Block size with pg_dump?
Date
Msg-id 200708270249.l7R2nfX00882@momjian.us
Whole thread Raw
In response to Re: Block size with pg_dump?  (Erik Jones <erik@myemma.com>)
Responses Re: Block size with pg_dump?  (Jean-David Beyer <jeandavid8@verizon.net>)
List pgsql-sql
Erik Jones wrote:
> >>> On the way back, likewise I could pipe the tape through dd before  
> >>> giving it
> >>> to pg_restore.
> >>>
> >>> Does pg_dump care what blocksize it gets? If so, what is it?
> >>
> >> I assume you could pipe pg_dump into dd and specify the block size in
> >> dd.
> >>
> > Of course on the way out I can do that.
> >
> > The main question is, If I present pg_restore with a 65536-byte  
> > blocksize
> > and it is expecting, e.g., 1024-bytes, will the rest of each block get
> > skipped? I.e., do I have to use dd on the way back too? And if so,  
> > what
> > should the blocksize be?
> 
> Postgres (by default) uses 8K blocks.

That is true of the internal storage, but not of pg_dump's output
because it is using libpq to pull rows and output them in a stream,
meaning there is no blocking in pg_dumps output itself.

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-sql by date:

Previous
From: Erik Jones
Date:
Subject: Re: Block size with pg_dump?
Next
From: Tom Lane
Date:
Subject: Re: List of FKeys ?