| From: | silly sad <sad(at)bestmx(dot)ru> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Top five challenges |
| Date: | 2011-03-10 17:15:34 |
| Message-ID: | 4D790736.2010302@bestmx.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-www |
On 03/10/11 20:07, Adrian Klaver wrote:
> On 03/10/2011 08:53 AM, silly sad wrote:
>
>
>>>
>>> Well, 'epoch' clearly is a point in time with the hour being midnight at
>>> GMT, so I don't see a problem with epoch making such an adjustment:
>>
>>
>> great! the flexible epoch!
>>
>> when do want to point an epoch to?
>> just set timezone and enjoy.
>>
>
> I am not sure what your point is.
my point is:
SELECT extract('epoch' from 'epoch'::timestamp);
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2011-03-10 17:48:46 | Re: Top five challenges |
| Previous Message | Adrian Klaver | 2011-03-10 17:07:09 | Re: Top five challenges |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2011-03-10 17:17:14 | Re: Read uncommitted ever possible? |
| Previous Message | Adrian Klaver | 2011-03-10 17:07:09 | Re: Top five challenges |