| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Bill Thoen <bthoen(at)gisnet(dot)com>, Andrej Ricnik-Bay <andrej(dot)groups(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PG Seg Faults Performing a Query |
| Date: | 2007-08-22 13:42:18 |
| Message-ID: | 20070822134218.GB32099@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Martijn van Oosterhout escribió:
> That said, it would be nice if it returned an error instead of
> crashing.
In my opinion it isn't just a matter of "would be nice". It is a
possible bug that should be investigated.
A look at a stack trace from the crashing process would be the first
place to start. In order to do that, please set "ulimit -c unlimited"
and rerun the query under psql. That should produce a core file. Then
run
gdb psql core
and inside gdb, execute "bt". Please send that output our way.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2007-08-22 14:31:29 | Re: could not open file "pg_clog/0BFF" |
| Previous Message | Martijn van Oosterhout | 2007-08-22 13:33:02 | Re: PG Seg Faults Performing a Query |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-08-22 13:52:07 | Re: A couple of tsearch loose ends |
| Previous Message | Martijn van Oosterhout | 2007-08-22 13:33:02 | Re: PG Seg Faults Performing a Query |