| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Richard Huxton <dev(at)archonet(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PITR Phase 2 - Design Planning |
| Date: | 2004-04-29 18:38:27 |
| Message-ID: | 1083263907.3100.12.camel@stromboli |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2004-04-29 at 16:09, 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.
>
Perhaps that was the inspiration, but no, I definitely meant a
CHECKPOINT.
But now you come to mention it, it would be better just to have a
command that simply wrote a named record to the xlog, so it can be
searched for later...
COMMENT [IN TRANSACTION LOG] 'starting payroll Feb04'
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Gardner | 2004-04-29 18:41:59 | Re: [HACKERS] What can we learn from MySQL? |
| Previous Message | Private | 2004-04-29 18:35:24 | PostgreSQL pre-fork speedup |