| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, mark(dot)watson(at)jurisconcept(dot)ca |
| Subject: | Re: Infinity bsearch crash on Windows |
| Date: | 2011-05-12 06:43:55 |
| Message-ID: | 4DCB81AB.4080600@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>> SELECT 'INFINITY'::TIMESTAMP;
>>
>
> Hmm ... I bet this is related to the recent reports about ALTER USER
> VALID UNTIL 'infinity' crashing on Windows. Can the people seeing this
> get through the regression tests? Perhaps more to the point, what is
> their setting of TimeZone? What does the pg_timezone_abbrevs view show
> for them?
>
I must have missed that thread, I think I'm missing one of these lists
(pgsql-bugs maybe?). I've cc'd Mark Watson so maybe you can get better
responses without me in the middle if needed; for this one, he reports:
Show timezone gives US/Eastern
Select * from pg_timezone_abbrevs returns zero rows
My Linux system that doesn't have this problem is also in US/Eastern,
too, but I get 189 rows in pg_timezone_abrevs.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kishwar deeba | 2011-05-12 06:52:38 | |
| Previous Message | Peter Eisentraut | 2011-05-12 05:22:36 | Re: pg_upgrade and PGPORT |