| 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-25 18:56:47 |
| Message-ID: | 20030325105134.Q42188-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.
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 a question: What is with the folowing statement in the log?
> 2003-03-25 18:42:27 [3531] LOG: query: UPDATE ONLY "public"."p_title" SET "name_id" = NULL WHERE "name_id" = $1
> Why is set to NULL when it fact it should be set to default (in this case 0) according to
> the "on delete set default" from p_title definition?
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql-bugs | 2003-03-25 21:25:47 | Bug #919: Can't initialize a database cluster in Cygwin/PostgreSQL 7.3.2 |
| Previous Message | Adrian Pop | 2003-03-25 18:41:37 | Postgresql 7.3.2 Crash |