From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Forcing current WAL file to be archived |
Date: | 2006-07-25 15:07:50 |
Message-ID: | 10061.1153840070@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Where are we on these TODO items:
> o Allow point-in-time recovery to archive partially filled
> write-ahead logs [pitr]
I believe we'd agreed that the necessary infrastructure for this is
just a function to tell the current WAL segment name and offset.
> o Automatically force archiving of partially-filled WAL files when
> pg_stop_backup() is called or the server is stopped
I see no need for that to be "automatic". I'd vote for a simple
function pg_finish_wal_segment() or something like that, which you
call just after pg_stop_backup() if you want this behavior. Trying
to tie it into pg_stop_backup() will only make things more complicated
and less flexible.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-07-25 15:17:59 | Re: plPHP and plRuby |
Previous Message | Bruce Momjian | 2006-07-25 14:51:17 | Forcing current WAL file to be archived |