Stephan Szabo <[EMAIL PROTECTED]> writes:
> That's because the set default uses a pretty ugly hack. It plans the
> query with =NULL and then replaces the NULL with the default value's
> stored plan info. My first guess is that it's something with this that's
> causing the crash.
I've applied the
Stephan Szabo <[EMAIL PROTECTED]> writes:
> Either way works for me. :) I'd guess it should look more like the default
> inserting stuff in copy for getting the expression's value. Doesn't look
> too hard to change (might take me a couple of days due to work, but I
> don't think that'll be a big i
On Thu, 27 Mar 2003, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > That's because the set default uses a pretty ugly hack. It plans the
> > query with =NULL and then replaces the NULL with the default value's
> > stored plan info. My first guess is that it's something with thi
Stephan Szabo <[EMAIL PROTECTED]> writes:
> That's because the set default uses a pretty ugly hack. It plans the
> query with =NULL and then replaces the NULL with the default value's
> stored plan info. My first guess is that it's something with this that's
> causing the crash.
Yeah, it's faili
On Wed, 26 Mar 2003, Adrian Pop wrote:
>
> > 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 differen
On Tue, 25 Mar 2003, Stephan Szabo wrote:
> 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.
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)
b
On Tue, 25 Mar 2003, Adrian Pop wrote:
> I have a postgresql 7.3.2 crash.
> Below you have the details.
Hmm, I can reproduce this with current sources. Backtrace from core
looks like a bug in the setdefault trigger (I'm at work so I don't
have real access to source to get more details).
> Now
Hello,
I have a postgresql 7.3.2 crash.
Below you have the details.
All the files included here can be found at:
http://www.ida.liu.se/~adrpo/postgresqlbug/
Operating systems (uname -a)
1: SunOS xxx.xxx.liu.se 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10
2: Linux dostoievsky 2.4.18-27.8.0
