| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com> |
| Cc: | Mark Dilger <hornschnorter(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Integer overflow in timestamp[tz]_part() and date/time boundaries check |
| Date: | 2016-03-17 13:58:06 |
| Message-ID: | 26490.1458223086@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com> writes:
> Is there any reason to leave JULIAN_MINDAY and JULIAN_MAXDAY which are
> not used now?
Those are just there to document what the limits really are. Possibly
some code would need them in future.
> Also why JULIAN_MAXMONTH is set to "6" whereas
> {DATE|TIMESTAMP}_END_JULIAN use "1" as month?
Because we're intentionally allowing a wider range for IS_VALID_JULIAN
than for IS_VALID_DATE/TIMESTAMP.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marisa Emerson | 2016-03-17 13:58:53 | Re: Proposal: BSD Authentication support |
| Previous Message | Amit Kapila | 2016-03-17 13:54:45 | Re: Pushdown target list below gather node (WAS Re: WIP: Upper planner pathification) |