From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Richard Huxton <dev(at)archonet(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PITR Phase 2 - Design Planning |
Date: | 2004-04-29 18:10:06 |
Message-ID: | 20040429181006.GA3254@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 29, 2004 at 05:09:19PM +0200, Peter Eisentraut wrote:
> Simon Riggs wrote:
> > I'd suggest extending the CHECKPOINT command so you can say:
> > CHECKPOINT <text message>
> > e.g. CHECKPOINT 'starting payroll Feb04';
> > (I'm sure some other DBMS does this...head spinning can;t recall...)
> > the text could just appear in the xlog record data packet...
>
> I believe you are thinking of a savepoint rather than a checkpoint.
But a "savepoint" has a very precise meaning in the SQL standard, which
relates to points in a transaction you can roll back to. I don't think
you want to overload with this other meaning, which I see as putting a
special mark in the XLog -- completely unrelated.
ISTM Checkpoint 'something' would flush all xlogs, insert some kind of
special xlog record with 'something' on it, and then archive everything
(up to that point?).
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"XML!" Exclaimed C++. "What are you doing here? You're not a programming
language."
"Tell that to the people who use me," said XML.
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2004-04-29 18:10:10 | Re: Call for 7.5 feature completion |
Previous Message | Chris Travers | 2004-04-29 18:02:19 | Re: What can we learn from MySQL? |