Re: to_char() causes backend to close connection
От | Karel Zak |
---|---|
Тема | Re: to_char() causes backend to close connection |
Дата | |
Msg-id | Pine.LNX.3.96.1001214133137.13007A-100000@ara.zf.jcu.cz обсуждение исходный текст |
Ответ на | to_char() causes backend to close connection (Kovacs Zoltan Sandor <tip@pc10.radnoti-szeged.sulinet.hu>) |
Ответы |
Re: to_char() causes backend to close connection
|
Список | pgsql-sql |
On Thu, 14 Dec 2000, Kovacs Zoltan Sandor wrote: > Hi, this query gives different strange results: > > select to_char(now()::abstime,'YYMMDDHH24MI'); the result: ERROR: to_char/to_number(): not unique decimal poit is right, because we have two to_char(): to_char(int, text) to_char(timestamp, text) and for 'now()::abstime' function manager select "number" version instead timestamp. And in "number" version is D as decimal point. > I get e.g. a "backend closed the channel unexpectedly..." error with > successful or failed resetting attempt (indeterministic) Yes this is a bug to_char() ... I fix it today. > My machine works with PostgreSQL 7.0.2 + Red Hat 6.1. > Is this fixed in 7.0.3? A problem (IMHO it's not problem) with 'now()::abstime' is in 7.1 too. But why you not use directly now()? Thanks! Karel
В списке pgsql-sql по дате отправления: