| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: Commit timestamp |
| Date: | 2007-01-26 00:41:48 |
| Message-ID: | 15256.1169772108@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> On 1/25/2007 6:47 PM, Neil Conway wrote:
>> Would this feature have any use beyond the specific project/algorithm
>> you have in mind?
> The tablelog project on pgfoundry currently uses the transactions start
> time but would be very delighted to have the commit time available instead.
BTW, it's not clear to me why you need a new log area for this. (We
don't log transaction start time anywhere, so certainly tablelog's needs
would not include it.) Commit timestamps are available from WAL commit
records in a crash-and-restart scenario, so wouldn't that be enough?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2007-01-26 00:42:24 | Re: Proposal: Commit timestamp |
| Previous Message | Tom Lane | 2007-01-26 00:33:10 | Re: Proposal: Change of pg_trigger.tg_enabled and adding pg_rewrite.ev_enabled |