| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alex Hunsaker <badalex(at)gmail(dot)com> |
| Cc: | depesz(at)depesz(dot)com, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Bad interval conversion? |
| Date: | 2009-08-18 16:42:19 |
| Message-ID: | 24633.1250613739@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alex Hunsaker <badalex(at)gmail(dot)com> writes:
> It only happens if you have integer date times on... seems to have
> gotten introduced by
> http://archives.postgresql.org/pgsql-committers/2008-03/msg00406.php
Uh, no, fsec_t was int32 before that (look towards the bottom of the
diff). I'm fairly dubious that fixing it as you suggest is a one-liner
--- the width of fsec_t is something that seems likely to propagate all
over. A narrower fix for whatever this specific problem is seems safer.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ali Al-Aswad | 2009-08-18 17:38:32 | BUG #4994: Silent Installation |
| Previous Message | Jaime Casanova | 2009-08-18 16:35:36 | Re: BUG #4993: memory issue with array_agg |