| From: | Werner Bohl <wbohl(at)deepdata(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1158: tsearch2 trigger crashes machine |
| Date: | 2004-05-31 06:06:28 |
| Message-ID: | 1085983587.19968.3.camel@sirio.sii |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, 2004-05-30 at 22:45, Tom Lane wrote:
> "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> writes:
> > Linux is severly affected and the machine needs a RESET to be able to boot.
> > (shutdown nor init 6 work!!)
>
> Sure you're not looking at hardware problems? PG should certainly not
> be able to crash a properly functioning kernel (since PG isn't a
> privileged process) and I haven't heard many complaints against later
> 2.4 series kernels either. My money is on flaky hardware...
>
Running the bulk insert process without the trigger does work well. We
did an update to the tsvector afterwards and it also worked without a
hitch. Therefore I suspect of the trigger.
TIA,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PostgreSQL Bugs List | 2004-05-31 08:09:39 | BUG #1159: server closed the connection unexpectedly |
| Previous Message | Tom Lane | 2004-05-31 04:45:12 | Re: BUG #1158: tsearch2 trigger crashes machine |