Re: [HACKERS] Failure in commit_ts tap tests
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] Failure in commit_ts tap tests |
Дата | |
Msg-id | 26339.1485013196@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] Failure in commit_ts tap tests (Pavan Deolasee <pavan.deolasee@gmail.com>) |
Ответы |
Re: [HACKERS] Failure in commit_ts tap tests
|
Список | pgsql-hackers |
Pavan Deolasee <pavan.deolasee@gmail.com> writes: > I think I understand why it's only affecting me and not others. > I've PGDATESTYLE set to "Postgres, MDY" in my bashrc and that formats the > commit timestamp as "Fri Jan 20 07:59:52.322811 2017 PST". If I unset that, > the result comes in a format such as "2017-01-20 21:31:47.766371-08". > Looks like perl doesn't throw an error if it can parse the leading part of > the string as a numeric. It still throws a warning, but the test passes. Hm, but what of the "null" value? Also, I get $ perl -e 'use warnings; use Test::More; ok("2017-01-01" != "null", "ok");' Argument "null" isn't numeric in numeric ne (!=) at -e line 1. Argument "2017-01-01" isn't numeric in numeric ne (!=) at -e line 1. ok 1 - ok # Tests were run but no plan was declared and done_testing() was not seen. regards, tom lane
В списке pgsql-hackers по дате отправления: