| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, 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: | 2018-07-10 02:33:45 |
| Message-ID: | CAMsr+YG5hxJjonNz-hcgzKakZd06LSL9t2593T87Q1--coCM0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10 July 2018 at 10:32, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>
>
>> I think it's probably a good idea to make it very explicit when moving
>> between big and small transaction IDs, hence the including of the word
>> 'big' in variable and function names and the use of a function-like
>> macro (rather than implicit conversion, which C doesn't give me a good
>> way to prevent).
>
>
> The only way I know of to prevent it is to use a wrapper by-value struct.
>
>
... and that's what I get for not finishing the thread before replying.
Anyway, please consider the other point re txid_current() and the user
facing xid type.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-07-10 02:40:14 | Re: Usage of epoch in txid_current |
| Previous Message | Craig Ringer | 2018-07-10 02:32:44 | Re: Usage of epoch in txid_current |