| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Steve Singer <steve(at)ssinger(dot)info>, Andres Freund <andres(at)2ndquadrant(dot)com>, Anssi Kääriäinen <anssi(dot)kaariainen(at)thl(dot)fi>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
| Subject: | Re: tracking commit timestamps |
| Date: | 2014-11-13 04:28:18 |
| Message-ID: | CAB7nPqTEh2eczkc6DUitFzv_f680Mh1EoS9HdyxX+NkbfbZCyw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
On Thu, Nov 13, 2014 at 7:56 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> On 11/12/14, 7:06 AM, Petr Jelinek wrote:
>>
>> - if the xid passed to get interface is out of range -infinity timestamp
>> is returned (I think it's bad idea to throw errors here as the valid range
>> is not static and same ID can start throwing errors between calls
>> theoretically)
>
>
> Wouldn't NULL be more appropriate?
Definitely. Defining a given value for information not valid is awkward.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2014-11-13 05:59:12 | Re: Race in "tablespace" test on Windows |
| Previous Message | Michael Paquier | 2014-11-13 03:42:27 | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-11-13 06:04:06 | Re: tracking commit timestamps |
| Previous Message | Jim Nasby | 2014-11-12 22:56:36 | Re: tracking commit timestamps |