From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Erik Jones <erik(at)myemma(dot)com> |
Cc: | Jean-David Beyer <jeandavid8(at)verizon(dot)net>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Block size with pg_dump? |
Date: | 2007-08-27 02:49:41 |
Message-ID: | 200708270249.l7R2nfX00882@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-27 03:48:32 | Re: List of FKeys ? |
Previous Message | Erik Jones | 2007-08-27 02:41:10 | Re: Block size with pg_dump? |