| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: regression failure on master with --disable-integer-datetimes |
| Date: | 2014-05-08 02:57:39 |
| Message-ID: | 20140508025739.GC1355372@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, May 06, 2014 at 03:39:52PM -0400, Noah Misch wrote:
> It seems I also broke the ecpg test suite under --disable-integer-datetimes.
> I think (not tested) the fix is s/123456789/123456123/ in dt_test2.pgc,
> because it rounds under float datetimes and truncates under integer datetimes.
Besides that, one of the new combinations had the same insufficient-precision
problem that affected interval.sql. With your commit and the attached patch,
"make check-world" looks good under --disable-integer-datetimes.
--
Noah Misch
EnterpriseDB http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| ecpg-check-float-date-v1.patch | text/plain | 2.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2014-05-08 08:07:49 | Re: Re: [BUGS] BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password |
| Previous Message | Jeff Davis | 2014-05-08 02:34:17 | Re: can insert timestamp value that can't be read |