| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Cc: | Adrian Pop <adrpo(at)ida(dot)liu(dot)se>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Postgresql 7.3.2 Crash |
| Date: | 2003-03-27 15:22:01 |
| Message-ID: | 11670.1048778521@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> 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 failing to allow for the possible need to insert a type
coercion step. This code shouldn't be here at all, really --- it should
be using build_column_default instead of messing about with the
default expression directly. I can fix it, unless you want to...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-03-27 15:34:30 | Re: Postgresql 7.3.2 Crash |
| Previous Message | pgsql-bugs | 2003-03-27 10:30:20 | Bug #922: PANIC: open of /scratch/production_2/pg_clog/0996 failed: No such file or directory |