| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | "Ragnar =?iso-8859-1?Q?Kj=F8rstad?=" <postgres(at)ragnark(dot)vestdata(dot)no> |
| Cc: | pgsql-ports(at)postgreSQL(dot)org |
| Subject: | Re: [PORTS] Port Bug Report: CURRENT_DATE problem |
| Date: | 1999-02-01 13:47:56 |
| Message-ID: | 36B5B08C.BEC247C4@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-ports |
> Summary: CURRENT_DATE problem
> System Configuration
> --------------------
> Operating System : RedHat 5.1 alpha, linux 2.0.35
> PostgreSQL version : 6.3.2
> Problem Description:
> --------------------
> When I use "SELECT CURRENT_DATE" postgres returns 10-03-2135...
> If I change the system-date, the CURRENT_DATE is changed accordingly
<snip>
> I've tried the same configuration on a redhat 5.1 intel-system, and
> there it works fine. I've tried mailling on the admin-maillinglist
> but didn't get any replies.
I know people have worked on this recently. Try upgrading to v6.4.2 and
if it still doesn't work then we'll find some patches which help.
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas G. Lockhart | 1999-02-01 14:10:48 | Re: [PORTS] Port Bug Report: Can't import nullable date field with COPY in psql |
| Previous Message | Thomas G. Lockhart | 1999-02-01 13:43:45 | Re: [PORTS] Port Bug Report: compile failed with byacc had to install bison |