[Postgres-xl-bugs] now() misbehaviour

asvany asvany at gmail.com
Mon Jan 25 05:29:03 PST 2016


I was check this issue almost every day , and now I can confirm it works
well.

It produces the required output:

test=# SELECT version(),now();
                                                    
version                                                    
|              now             
-----------------------------------------------------------------------------------------------------------------+-------------------------------
 PostgreSQL 9.5.0 (Postgres-XL 9.5beta1) on x86_64-pc-linux-gnu,
compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit | *2016-01-25
14:27:33.820489+01*
(1 row)


Thanks!



On 12/17/2015 05:55 PM, Pavan Deolasee wrote:
>
>
> On Thu, Dec 17, 2015 at 10:14 PM, asvany <asvany at gmail.com
> <mailto:asvany at gmail.com>> wrote:
>
>     Hi developers,
>
>     unfortunately the now() function is not works.
>     always produces the same output:
>
>     SELECT version(),now(); 
>
>     output:
>
>                                                          
>     version                                                      
>     |          now          
>     --------------------------------------------------------------------------------------------------------------------+------------------------
>      PostgreSQL 9.5beta1 (Postgres-XL 9.5beta1) on
>     x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2,
>     64-bit | *2000-01-01 01:00:00+01**
>     *
>
>     I didn't find any workaround to detect the current time.
>
>
> Thanks for the report. Will look into it. I think it could be a
> regression after I recently committed fast-query-shipping to XL.
>
> Thanks,
> Pavan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.postgres-xl.org/private.cgi/postgres-xl-bugs-postgres-xl.org/attachments/20160125/063ad244/attachment.htm>


More information about the postgres-xl-bugs mailing list