pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jie Liang <jliang@ipinc.com>
To: pgsql-admin@postgresql.org
To: pgsql-sql@postgresql.org
Subject: need help urgent
Date: Fri, 03 Nov 2000 11:35:20 -0800
Message-ID: <3A031378.F6D5CA66@ipinc.com> (raw)

Hi,

Is anybody have experience about core dump?
We have some scripts have been used for a long time, however, recently,
they seem to have some problems,
the message I got:

SSELECT priority from priority where source=lower('questionable')
Total insert into preunchecked: 1
Segmentation fault - core dumped
Segmentation fault - core dumped

This script has been used for a few monthes, no problem.

I checked my pgsql.log, I saw:

Nov  3 00:58:45 wipeout postgres[1638]: query: INSERT INTO
source(id,source) SELECT id,'questionable' from
preunchecked                 WHERE insertdate>= '2000-11
-03 00:58:45-08'
Nov  3 00:58:46 wipeout postgres[1642]: query: SELECT version()
Nov  3 00:58:46 wipeout postgres[1642]: query: begin
Nov  3 00:58:46 wipeout postgres[1642]: ProcessUtility: begin
Nov  3 00:58:46 wipeout postgres[1642]: query: set transaction isolation
level serializable
Nov  3 00:58:46 wipeout postgres[1642]: ProcessUtility: set transaction
isolation level serializable
Nov  3 00:58:46 wipeout postgres[1642]: query: SELECT oid from
pg_database where datname = 'template1'
Nov  3 00:58:46 wipeout postgres[1642]: query: SELECT pg_type.oid,
typowner, typname, typlen, typprtlen, typinput, typoutput, typreceive,
typsend, typelem, typdeli
m, typdefault, typrelid, typbyval, usename from pg_type, pg_user where
typowner = usesysid
Nov  3 00:58:46 wipeout postgres[1642]: query: SELECT pg_proc.oid,
proname, prolang, pronargs, prorettype, proretset, proargtypes, prosrc,
probin, usename from pg_
proc, pg_user where pg_proc.oid > '17216'::oid and proowner = usesysid
Nov  3 00:58:46 wipeout postgres[1642]: query: SELECT pg_aggregate.oid,
aggname, aggtransfn1, aggtransfn2, aggfinalfn, aggtranstype1,
aggbasetype, aggtranstype2, a
gginitval1, agginitval2, usename from pg_aggregate, pg_user where
aggowner = usesysid

................

We have no script to open a new session[1642],  how this happen? how I
to prevent this??


Thanks!


--
Jie LIANG

Internet Products Inc.

10350 Science Center Drive
Suite 100, San Diego, CA 92121
Office:(858)320-4873

jliang@ipinc.com
www.ipinc.com






Message-ID: <3A031378.F6D5CA66@ipinc.com>
Permalink:  ../3A031378.F6D5CA66@ipinc.com/
Also on:    postgresql.org/message-id/3A031378.F6D5CA66@ipinc.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: jliang@ipinc.com, pgsql-admin@postgresql.org
  Subject: Re: need help urgent
  In-Reply-To: <3A031378.F6D5CA66@ipinc.com>
  References: <3A031378.F6D5CA66@ipinc.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox