Re: proposal: rounding up time value less than its unit.

From: Greg Stark <stark(at)mit(dot)edu>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomonari Katsumata <t(dot)katsumata1122(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Subject: Re: proposal: rounding up time value less than its unit.
Date: 2014-09-23 19:05:16
Message-ID: CAM-w4HMyvEggFhTp6wnVtFuqo-3+=fK00-vsNmLnD=unUhdaMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fwiw I agree with TL2. The simplest, least surprising behaviour to explain
to users is to say we round to nearest and if that means we rounded to zero
(or another special value) we throw an error. We could list the minimum
value in pg_settings and maybe in documentation.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-09-23 19:36:48 Re: add modulo (%) operator to pgbench
Previous Message Alvaro Herrera 2014-09-23 19:04:46 Re: BRIN indexes - TRAP: BadArgument