From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Adrian Pop <adrpo(at)ida(dot)liu(dot)se> |
Cc: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Postgresql 7.3.2 Crash |
Date: | 2003-03-26 07:17:12 |
Message-ID: | 20030325230637.T54025-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, 25 Mar 2003, Adrian Pop wrote:
> I have a postgresql 7.3.2 crash.
> Below you have the details.
Okay, I think I've localized the cause (but not a fix).
> name_id bigint not null default 0,
I think the problem occurs with of the hack (mentioned in the last mail)
because the default expression is of a different type. I think it occurs
specifically because the default expression is of a by value type and the
real type is by reference, but I haven't gone through enough tests to be
sure (it works if I make the default a bigint, a timestamp column with a
timestamptz expression works but an abstime doesn't)
Short term workaround is to make the default expression of the same type
as the column rather than merely something that can be converted to
that type.
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Rubio | 2003-03-26 07:49:15 | Re: Can't connect to my postgresql |
Previous Message | pgsql-bugs | 2003-03-26 06:49:47 | Bug #920: The PostgreSql Server goes down |