Re: Exposing the stats snapshot timestamp to SQL
| От | Matt Kelly |
|---|---|
| Тема | Re: Exposing the stats snapshot timestamp to SQL |
| Дата | |
| Msg-id | CA+KcUkiR+54mX1528tTAZx4PeCeqrYax7gdv3ANL1y1hfKT6Ww@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Exposing the stats snapshot timestamp to SQL (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Exposing the stats snapshot timestamp to SQL
|
| Список | pgsql-hackers |
On Thu, Jan 29, 2015 at 8:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Matt Kelly <mkellycs@gmail.com> writes:
> Jim, I'm not sure I understand what you mean? This new function follows
> the same conventions as everything else in the file. TimestampTz is just a
> typedef for int64.
... or double. Have you checked that the code behaves properly with
--disable-integer-timestamps?
regards, tom lane
Well, yes int or double. I should have been more clear about that. Its a good point though that I should run the server with disable for completeness.
I presume you meant --disable-integer-datetimes. I just ran that test case now, all set.
For my own edification, was there really any risk of something so trivial breaking due to that setting, or was it just for completeness? (which is a perfectly valid reason)
Thanks,
- Matt K.
В списке pgsql-hackers по дате отправления: