pg.ddx.io pgsql-hackers-pitr@postgresql.org mailing list archive
help / color / mirror / Atom feedUpdate on PITR
10+ messages / 8 participants
[nested] [flat]
* Update on PITR
@ 2004-03-30 21:19 Simon Riggs <simon@2ndquadrant.com>
0 siblings, 1 reply; 10+ messages in thread
From: Simon Riggs @ 2004-03-30 21:19 UTC (permalink / raw)
To: pgsql-hackers@postgresql.org
A brief update on PITR status:
I've completed successful unit testing of the PostgreSQL client-side
code for the XLogArchive API. Just about to start moving on to pg_arch
and the archiver side code. At this rate, I should have a
system-testable set of patches in around 2 weeks time for the first
phase of PITR. I'll release the code as soon as I can: I'm conscious
that other work may be updating xlog code also and I'm sure the
committers will want some thorough checks before acceptance.
Quick update on overall plan:
Phase 1: xlog archiving api, with functional pg_arch utility
- ETA mid-April
- changes so far to xlog.c, xlog.h, guc.c
- will allow rollforward along extended archive history till-end of
logs, diskspace permitting
Phase 2: add code to control recovery (to a point-in-time)
- should be there by mid-May, though may yield more quickly
- will allow rollforward along extended archive history to point in
time, diskspace permitting
Phase 3: various additional tweaks, suggestions & better documentation
- early June (following some time travelling in May)
- will allow rollforward along extended archive history to point in
time, even when logs > available disk
Is this all still OK for 7.5? (My attempts at cataloguing changes has
fallen by the wayside in concentrating on the more important task of
PITR.) Do we have a planned freeze month yet?
...Those with a wry sense of humour may be interested to know that I
recently lost my hard-drive on my main business workstation. Not
uncommon, I grant you, but in the circumstances I didn't really need the
extra recovery practice...
Best Regards, Simon Riggs
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Update on PITR
@ 2004-03-31 16:35 Tom Lane <tgl@sss.pgh.pa.us>
parent: Simon Riggs <simon@2ndquadrant.com>
0 siblings, 4 replies; 10+ messages in thread
From: Tom Lane @ 2004-03-31 16:35 UTC (permalink / raw)
To: Simon Riggs <simon@2ndquadrant.com>; +Cc: pgsql-hackers@postgresql.org
"Simon Riggs" <simon@2ndquadrant.com> writes:
> [ expecting to finish PITR by early June ]
> Is this all still OK for 7.5? (My attempts at cataloguing changes has
> fallen by the wayside in concentrating on the more important task of
> PITR.) Do we have a planned freeze month yet?
There's not really a plan at the moment, but I had June in the back of
my head as a good time; it looks to me like the Windows port will be
stable enough for beta in another month or two, and it'd be good if
PITR were ready to go by then.
Is your timeline based on the assumption of doing all the work yourself?
If so, how about farming out some of it? I'd be willing to contribute
some effort to PITR. (It's been made clear to me that Red Hat really
wants PITR in 7.5 ;-))
regards, tom lane
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: [HACKERS] Update on PITR
@ 2004-03-31 18:25 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Tom Lane <tgl@sss.pgh.pa.us>
3 siblings, 1 reply; 10+ messages in thread
From: Bruce Momjian @ 2004-03-31 18:25 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Simon Riggs <simon@2ndquadrant.com>; pgsql-hackers-pitr
Tom Lane wrote:
> "Simon Riggs" <simon@2ndquadrant.com> writes:
> > [ expecting to finish PITR by early June ]
>
> > Is this all still OK for 7.5? (My attempts at cataloguing changes has
> > fallen by the wayside in concentrating on the more important task of
> > PITR.) Do we have a planned freeze month yet?
>
> There's not really a plan at the moment, but I had June in the back of
> my head as a good time; it looks to me like the Windows port will be
> stable enough for beta in another month or two, and it'd be good if
> PITR were ready to go by then.
>
> Is your timeline based on the assumption of doing all the work yourself?
> If so, how about farming out some of it? I'd be willing to contribute
> some effort to PITR. (It's been made clear to me that Red Hat really
> wants PITR in 7.5 ;-))
Agreed! Lets see if we can assemble a team to start coding PITR.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Update on PITR
@ 2004-03-31 18:30 Stephen Frost <sfrost@snowman.net>
parent: Tom Lane <tgl@sss.pgh.pa.us>
3 siblings, 0 replies; 10+ messages in thread
From: Stephen Frost @ 2004-03-31 18:30 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Simon Riggs <simon@2ndquadrant.com>; pgsql-hackers@postgresql.org
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> Is your timeline based on the assumption of doing all the work yourself?
> If so, how about farming out some of it? I'd be willing to contribute
> some effort to PITR. (It's been made clear to me that Red Hat really
> wants PITR in 7.5 ;-))
Hey, us Debian folks really want it too. ;)
Stephen
Attachments:
signature.asc (application/pgp-signature, 188B) download
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Update on PITR
@ 2004-03-31 18:42 Devrim GUNDUZ <devrim@gunduz.org>
parent: Tom Lane <tgl@sss.pgh.pa.us>
3 siblings, 0 replies; 10+ messages in thread
From: Devrim GUNDUZ @ 2004-03-31 18:42 UTC (permalink / raw)
To: pgsql-hackers@postgresql.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Wed, 31 Mar 2004, Tom Lane wrote:
<snip>
> I'd be willing to contribute some effort to PITR. (It's been made clear
> to me that Red Hat really wants PITR in 7.5 ;-))
Wow! That's exciting news :-) Does Red Hat also want some more enterprise
features? ;-)
I've been using PostgreSQL since... about 5 years... The great improvement
since then really impresses me.
Regards,
- --
Devrim GUNDUZ
devrim@gunduz.org devrim.gunduz@linux.org.tr
http://www.TDMSoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFAaxEytl86P3SPfQ4RAkisAKDoa8yXf9a68TqBabO6uipPwbihxgCdEJoo
0tkna1hIXkCWFsGcINl+gWs=
=bNf3
-----END PGP SIGNATURE-----
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: [HACKERS] Update on PITR
@ 2004-03-31 20:33 Simon Riggs <simon@2ndquadrant.com>
parent: Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 0 replies; 10+ messages in thread
From: Simon Riggs @ 2004-03-31 20:33 UTC (permalink / raw)
To: Bruce Momjian <pgman@candle.pha.pa.us>; Tom Lane <tgl@sss.pgh.pa.us>; sfrost@snowman.net; +Cc: pgsql-hackers@postgresql.org; pgsql-hackers-pitr
>Bruce Momjian wrote
> Tom Lane wrote:
> > "Simon Riggs" <simon@2ndquadrant.com> writes:
> > > [ expecting to finish PITR by early June ]
> >
> > > Is this all still OK for 7.5? (My attempts at cataloguing
> changes has
> > > fallen by the wayside in concentrating on the more
> important task of
> > > PITR.) Do we have a planned freeze month yet?
> >
> > There's not really a plan at the moment, but I had June in
> the back of
> > my head as a good time; it looks to me like the Windows port will be
> > stable enough for beta in another month or two, and it'd be good if
> > PITR were ready to go by then.
> >
> > Is your timeline based on the assumption of doing all the
> work yourself?
> > If so, how about farming out some of it? I'd be willing to
> contribute
> > some effort to PITR. (It's been made clear to me that Red
> Hat really
> > wants PITR in 7.5 ;-))
>
> Agreed! Lets see if we can assemble a team to start coding PITR.
>
Thank you all for your offers of help. Yes, is the short answer; we
should be able to cut enough code on independent work streams to get
this system testable by end April.
As I say, I started coding some time back and am well into what I've
called Phase 1, so its probably best for me to complete that. You guys
will be contributing by looking at my code anyhow, so your goodwill is
certainly going to be called in, don't worry. There isn't anything too
hairy code wise anyhow, if I'm honest. For clarity, this will give the
facility to archive xlogs beyond their current short lifetime in the
recycling method currently used.
Phase 2 is definitely another matter...There doesn't seem to be any
dependency that I can see for that.... I called it Phase 2 because, yes,
I did make the assumption that I was doing it all myself, but I did set
off on this journey as a team effort and I welcome that still...
I described this piece of work earlier as:
Phase 2: add code to control recovery (to a point-in-time)
- will allow rollforward along extended archive history to point in
time, diskspace permitting
In my earlier summary of all design contributions there was the idea for
a postmaster command line switch which would make rollforward recovery
stop at the appropriate place. Two switches were discussed:
i) roll forward to point in time. This sounds relatively easy...recovery
is already there, all you have to do is stop it at the right place...but
I haven't looked into the exact mechanism of reading the xlog headers
etc.. [There's also a few bits of work to do there in terms of putting
in hooks for the command mechanism.
Something like postmaster -R "2004/12/10 19:37:04" as a loose example
ii) roll forward on all available logs, but shutdown at end, leaving pg
in a recovery-pending state (still). This then gives the DBA a chance to
do either a) switch in a new batch of xlogs, allowing an infinite
sequence of xlogs to be applied one batch at a time, or b) keep a "hot
standby" system continually primed and ready to startup should the
primary go down.
Neither of those looks too hard to me, so should be able to be done by
about mid-April when I'm thinking to have finished XLogArchive API. As I
say there's no particular dependency on the XLogArchive API stuff all
working, since they can both be tested independently, though we must put
them together for system testing.
Further tasks (what I had thought of as "Phase 3", but again these can
be started now...)
- what to do should a cancel CTRL-C be issued during recovery..what
state is the database left in?
- How do you say "this is taking to long, I really need my database up
now, whatever state its in" (when recovery is grinding away, not before
you start it or after it has failed, which is where you would use
pg_resetxlog)....
- can you change your mind on that once its up and you see what a mess
its in! i.e. put it back into recovery? what would that take - saving
clogs? an optional "trial recovery" mode?
- how would we monitor a lengthy recovery? watch for "starting recovery
of log XXX" messages and do some math to work out the finish time, or is
there a better way?
- is it possible to have parallel recovery processes active
simultaneously for faster recovery?? can we work anything into the
design now that would allow that to be added later?
What I think is really important is a very well coordinated test plan.
Perhaps even more importantly a test plan not written by me, since I
might make some dangerous assumptions in writing it. Having a written
test plan would allow us to cover all the edge cases that PITR is
designed to recover from. It will be pretty hard for most production
users of PostgreSQL to fully test PITR, though of course many will "kick
the tyres" shall we say, to confirm a full implementation. Many of the
tests are not easily automatable, so we can't just dream up some more
regression tests. A written plan would then allow coordinated testing to
occur across platforms, so a QNX user may spot something that also
effects Solaris etc.. Is that anything any large open source outfit
(commercial or non-commerical) would be able to contribute the time of a
test analyst for 10 days to complete? ;) ...I didn't get a huge response
from the community when last I requested assistance in that area,
assuming my post got through.
Overall, I'm confident that we're getting close to this becoming fully
real. The main issues historically were that the xlogs didn't contain
all that was required for full recovery, but those challenges have been
solved already by J.R. and Patrick(subject to full system testing).
Best Regards,
Simon Riggs
2nd Quadrant
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Update on PITR
@ 2004-04-01 01:22 Christopher Kings-Lynne <chriskl@familyhealth.com.au>
parent: Tom Lane <tgl@sss.pgh.pa.us>
3 siblings, 2 replies; 10+ messages in thread
From: Christopher Kings-Lynne @ 2004-04-01 01:22 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Simon Riggs <simon@2ndquadrant.com>; pgsql-hackers@postgresql.org
> Is your timeline based on the assumption of doing all the work yourself?
> If so, how about farming out some of it? I'd be willing to contribute
> some effort to PITR. (It's been made clear to me that Red Hat really
> wants PITR in 7.5 ;-))
What is RedHat's interest in PostgreSQL? Last time I heard they weren't
interested in their database product anymore. Why do they care about
the PostgreSQL project?
Of course, it's awesome that they are - but why? What's their plan?
Chris
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Update on PITR
@ 2004-04-01 02:50 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
1 sibling, 0 replies; 10+ messages in thread
From: Bruce Momjian @ 2004-04-01 02:50 UTC (permalink / raw)
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; Simon Riggs <simon@2ndquadrant.com>; pgsql-hackers@postgresql.org
Christopher Kings-Lynne wrote:
> > Is your timeline based on the assumption of doing all the work yourself?
> > If so, how about farming out some of it? I'd be willing to contribute
> > some effort to PITR. (It's been made clear to me that Red Hat really
> > wants PITR in 7.5 ;-))
>
> What is RedHat's interest in PostgreSQL? Last time I heard they weren't
> interested in their database product anymore. Why do they care about
> the PostgreSQL project?
>
> Of course, it's awesome that they are - but why? What's their plan?
>
SRA wants PITR too, as does everyone else. :-)
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Update on PITR
@ 2004-04-01 03:25 Marc G. Fournier <scrappy@postgresql.org>
parent: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
1 sibling, 1 reply; 10+ messages in thread
From: Marc G. Fournier @ 2004-04-01 03:25 UTC (permalink / raw)
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; Simon Riggs <simon@2ndquadrant.com>; pgsql-hackers@postgresql.org
On Thu, 1 Apr 2004, Christopher Kings-Lynne wrote:
> > Is your timeline based on the assumption of doing all the work yourself?
> > If so, how about farming out some of it? I'd be willing to contribute
> > some effort to PITR. (It's been made clear to me that Red Hat really
> > wants PITR in 7.5 ;-))
>
> What is RedHat's interest in PostgreSQL? Last time I heard they weren't
> interested in their database product anymore. Why do they care about
> the PostgreSQL project?
Just speculation, but I'd go with end goal being to be able to dump Oracle
altogether, once PostgreSQL actually has all the various enterprise
features ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
^ permalink raw reply [nested|flat] 10+ messages in thread
* Re: Update on PITR
@ 2004-04-01 19:42 Chris Browne <cbbrowne@acm.org>
parent: Marc G. Fournier <scrappy@postgresql.org>
0 siblings, 0 replies; 10+ messages in thread
From: Chris Browne @ 2004-04-01 19:42 UTC (permalink / raw)
To: " <pgsql-advocacy@postgresql.org.pgsql-hackers>
scrappy@postgresql.org ("Marc G. Fournier") writes:
> On Thu, 1 Apr 2004, Christopher Kings-Lynne wrote:
>> > Is your timeline based on the assumption of doing all the work
>> > yourself? If so, how about farming out some of it? I'd be
>> > willing to contribute some effort to PITR. (It's been made clear
>> > to me that Red Hat really wants PITR in 7.5 ;-))
>>
>> What is RedHat's interest in PostgreSQL? Last time I heard they
>> weren't interested in their database product anymore. Why do they
>> care about the PostgreSQL project?
>
> Just speculation, but I'd go with end goal being to be able to dump
> Oracle altogether, once PostgreSQL actually has all the various
> enterprise features ...
I understood that they were using Oracle Financials and possibly
Oracle Manufacturing for their internal systems; I seriously doubt
that Oracle will be adding support for PostgreSQL in those products
:-).
That being said, I'm sure it is in their interests to be able to
promote database options that do not mandate sending one penny to any
other vendors.
That was pretty clearly a major reason behind RHAT promoting GNOME
over KDE, in that "business" use of the latter would mandate sending
more money to a little company in Europe than RHAT would receive in
selling 50 'boxed sets.'
--
"cbbrowne","@","cbbrowne.com"
http://cbbrowne.com/info/wp.html
Rules of the Evil Overlord #145. "My dungeon cell decor will not
feature exposed pipes. While they add to the gloomy atmosphere, they
are good conductors of vibrations and a lot of prisoners know Morse
code." <http://www.eviloverlord.com/;
^ permalink raw reply [nested|flat] 10+ messages in thread
end of thread, other threads:[~2004-04-01 19:42 UTC | newest]
Thread overview: 10+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-03-30 21:19 Update on PITR Simon Riggs <simon@2ndquadrant.com>
2004-03-31 16:35 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-03-31 18:25 ` Bruce Momjian <pgman@candle.pha.pa.us>
2004-03-31 20:33 ` Simon Riggs <simon@2ndquadrant.com>
2004-03-31 18:30 ` Stephen Frost <sfrost@snowman.net>
2004-03-31 18:42 ` Devrim GUNDUZ <devrim@gunduz.org>
2004-04-01 01:22 ` Christopher Kings-Lynne <chriskl@familyhealth.com.au>
2004-04-01 02:50 ` Bruce Momjian <pgman@candle.pha.pa.us>
2004-04-01 03:25 ` Marc G. Fournier <scrappy@postgresql.org>
2004-04-01 19:42 ` Chris Browne <cbbrowne@acm.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox