Re: BUG #6046: select current_date crashes postgres

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Rikard Pavelic <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6046: select current_date crashes postgres
Date: 2011-06-01 00:29:12
Message-ID: 4DE587D8.3050705@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 1/06/2011 1:28 AM, Rikard Pavelic wrote:

> select current_time
> or select current_date
>
> results in postgres crash.

Ouch. That's not ideal.

Please post the messages output to the postgresql log file from when the
backend crashes. You will find the log file in the pg_log directory
inside your data directory, which by default is under the postgresql
installation directory in Program Files.

Are you running the 32-bit or 64-bit build of PostgreSQL 9.1 beta? Both
will run on 64-bit Windows.

Did you get it from EnterpriseDB
(http://www.enterprisedb.com/products-services-training/pgdevdownload) ?

--
Craig Ringer

Tech-related writing at http://soapyfrogs.blogspot.com/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Craig Ringer 2011-06-01 00:29:38 Re: BUG #6046: select current_date crashes postgres
Previous Message Rikard Pavelic 2011-05-31 17:28:27 BUG #6046: select current_date crashes postgres

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2011-06-01 00:29:38 Re: BUG #6046: select current_date crashes postgres
Previous Message Mark Kirkwood 2011-06-01 00:27:46 Re: patch review : Add ability to constrain backend temporary file space