From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PITR logging control program |
Date: | 2004-04-29 13:52:10 |
Message-ID: | 20040429135210.GC2258@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 29, 2004 at 12:18:38AM -0400, Bruce Momjian wrote:
> OK, I looked over the code. Basically it appears pg_arch is a
> client-side program that copies files from pg_xlog to a specified
> directory, and marks completion in a new pg_rlog directory.
>
> The driving part of the program seems to be:
>
> while ( (n = read( xlogfd, buf, BLCKSZ)) > 0)
> if ( write( archfd, buf, n) != n)
> return false;
>
> The program basically sleeps and when it awakes checks to see if new WAL
> files have been created.
Is the API able to indicate a written but not-yet-filled WAL segment?
So an archiver could copy the filled part, and refill it later. This
may be needed because a segment could take a while to be filled.
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Hoy es el primer día del resto de mi vida"
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-04-29 14:07:01 | Re: PITR logging control program |
Previous Message | Robert Bernier | 2004-04-29 13:26:37 | Re: What can we learn from MySQL? |