The following bug has been logged online:

Bug reference: 1500
Logged by: nagash
Email address: postgresql@nagash.org
PostgreSQL version: 8.0.1
Operating system: RedHat
Description: child dead
Details:

site_utf=# SELECT to_char(NOW() - '2000-10-02'::date, 'YYYYMonDD');
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.

tested on 2 servers and it show with exactly 'YYYYMonDD' if I write
SELECT to_char(NOW() - '2000-10-02'::date, 'YYYY');

it will be OK

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

"nagash" <postgresql@nagash.org> writes:
> site_utf=# SELECT to_char(NOW() - '2000-10-02'::date, 'YYYYMonDD');
> server closed the connection unexpectedly

Hmm, I get bad output rather than a core dump, but it certainly seems
like a "must fix" if a dump is possible. Karel, can you look into it?

regression=# select to_char('1605 days 12:09:35'::interval, 'YYYYMonDD');
to_char
-----------
0001Ä@16
(1 row)

regression=#

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Tom Lane wrote:
> "nagash" <postgresql@nagash.org> writes:
>
>>site_utf=# SELECT to_char(NOW() - '2000-10-02'::date, 'YYYYMonDD');
>>server closed the connection unexpectedly
>
>
> Hmm, I get bad output rather than a core dump, but it certainly seems
> like a "must fix" if a dump is possible. Karel, can you look into it?

I got sig-11 here (although that was with an 8.0 beta I had lying
around) - does it with intervals but not with dates.

--
Richard Huxton
Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings