| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Brendan Jurd <direvus(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net>, pg-dev <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: generate_series from now to infinity... |
| Date: | 2009-05-17 11:37:38 |
| Message-ID: | 0A5E0082-1745-4AAB-98B5-E8DD132866C3@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 16, 2009, at 11:58 PM, Brendan Jurd <direvus(at)gmail(dot)com> wrote:
> On Sun, May 17, 2009 at 1:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> "Dickson S. Guedes" <listas(at)guedesoft(dot)net> writes:
>>> Is a simple "SELECT generate_series(now(), CAST('infinity'::date AS
>>> timestamp), interval '1 hour');" working forever, an expected
>>> behavior?
>>
>> Uh, what were you expecting it to do?
>
> It appears that any generate_series involving infinity is guaranteed
> to fail.
>
> That being the case, wouldn't it be more useful to throw an error than
> to just keep on running until overflow?
What if it were combined with LIMIT?
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dickson S. Guedes | 2009-05-17 16:38:35 | Re: generate_series from now to infinity... |
| Previous Message | Brendan Jurd | 2009-05-17 03:58:41 | Re: generate_series from now to infinity... |