| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org,Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>,Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>,pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Usage of epoch in txid_current |
| Date: | 2017-12-05 18:07:28 |
| Message-ID: | CBC16911-4F09-4C74-9549-6A2D12854F0B@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On December 5, 2017 10:01:43 AM PST, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>Andres,
>
>* Andres Freund (andres(at)anarazel(dot)de) wrote:
>> I think it makes a fair bit of sense to not do the current crufty
>> tracking of xid epochs. I don't really how we got there, but it
>doesn't
>> make terribly much sense. Don't think we need additional WAL logging
>> though - we should be able to piggyback this onto the already
>existing
>> clog logging.
>
>Don't you mean xact logging? ;)
No. We log a WAL record at clog boundaries. Wraparounds have to be at one. We could just include the 64 bit xid there and would have reliable tracking.
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-12-05 18:25:25 | Re: [HACKERS] Transaction control in procedures |
| Previous Message | Robert Haas | 2017-12-05 18:04:43 | Re: [HACKERS] parallel.c oblivion of worker-startup failures |