| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <jim(at)nasby(dot)net> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] pg_sleep(interval) |
| Date: | 2013-10-21 13:07:35 |
| Message-ID: | CA+TgmoZzhPOqVR6E=RJFEfjhz9RLQ6bCTZOKkB=dvU4pza-pZQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 18, 2013 at 7:21 PM, Jim Nasby <jim(at)nasby(dot)net> wrote:
> Yeah, but hasn't every case of this that we've run into been directly
> related to casting problems, and not function or operator preference?
No.
> Something else I'm wondering is if priority should actually be something
> that's numbered instead of just a boolean. I can see far more logic to
> implicitly casting text to double than I can text to interval, but if a cast
> to double won't actually get you where you want and a cast to interval
> will... Maybe it's possible to account for all those cases with just a
> boolean... maybe not.
I wondered about this, too.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-10-21 13:15:36 | Re: Commitfest II CLosed |
| Previous Message | Colin 't Hart | 2013-10-21 12:40:42 | Re: psql built from git still reports 9.3devel |