From: | Danny <dannyh(at)idx(dot)com(dot)au> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | data type (datetime) |
Date: | 2000-09-21 11:42:16 |
Message-ID: | 00092122483002.00343@freebsd.freebsd.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
- Hello
- I have looked for a data type which allows me to have (using a cliche example
again) FlightDetail_Arrival whcih is like so 21:07:00 18:00
- When I type this in psql it changes my data type from datetime to "timestamp"
- It gives me the following about I did a SELECT * FROM table
- 21:07:00 18:00 + 11
- Question
1) How to i make the datatype to just "21:07:00 18:00" only
Lookinf gowrd to your feedback.
dannyh(at)idx(dot)com(dot)au
On Wed, 20 Sep 2000, Tom Lane wrote:
> Buddy Lee Haystack <haystack(at)email(dot)rentzone(dot)org> writes:
> > Here they are, but they seem as vague as the Apache error logs -to me anyway...
>
> You're right, not much info there except that a backend died untimely.
>
> Unless you had ulimit set to prevent it, the crashing backend should've
> left a core file in the database subdirectory it was connected to (ie,
> $PGDATA/base/DATABASENAME/core). If so, it'd be useful to see a stack
> trace from that file ... do you know how to get a stack trace with gdb?
> Copy the corefile to someplace safe, in any case; we may want to
> study it later.
>
> One thing that would be real helpful to know is exactly what query the
> failed backend was trying to execute. Perhaps you know that already.
> If not, but if you can reproduce the crash by rerunning your
> application, then restart the postmaster with "-d2" added to its command
> line arguments; that will cause each backend to log each query it
> executes.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alessio Bragadini | 2000-09-21 12:20:39 | Re: Re: Large Objects |
Previous Message | Alexey Borzov | 2000-09-21 09:40:23 | Resolved! (was: Re[8]: WTF is going on with PG_VERSION?) |