Re: PITR, checkpoint, and local relations

From: Richard Tucker <richt(at)multera(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "J(dot) R(dot) Nield" <jrnield(at)usol(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PITR, checkpoint, and local relations
Date: 2002-08-02 21:30:26
Message-ID: EKEKLEKKLDAEEKDBDMMAMEGDCDAA.richt@multera.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org]On Behalf Of Tom Lane
> Sent: Friday, August 02, 2002 5:25 PM
> To: J. R. Nield
> Cc: Richard Tucker; Bruce Momjian; PostgreSQL Hacker
> Subject: Re: [HACKERS] PITR, checkpoint, and local relations
>
>
> "J. R. Nield" <jrnield(at)usol(dot)com> writes:
> >> (In particular, I *strongly* object to using the buffer manager at all
> >> for reading files for backup. That's pretty much guaranteed
> to blow out
> >> buffer cache. Use plain OS-level file reads. An OS directory search
> >> will do fine for finding what you need to read, too.)
>
> > How do you get atomic block copies otherwise?
>
> Eh? The kernel does that for you, as long as you're reading the
> same-size blocks that the backends are writing, no?
If the OS block size is 4k and the PostgreSQL block size is 8k do we know
for sure that the write call does not break this into two 4k writes to the
OS buffer cache?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Tucker 2002-08-02 21:40:26 Re: PITR, checkpoint, and local relations
Previous Message Tom Lane 2002-08-02 21:29:09 Re: PITR, checkpoint, and local relations