Re: Re: backend closing connections while executing... - Mailing list pgsql-general
From | Anand Raman |
---|---|
Subject | Re: Re: backend closing connections while executing... |
Date | |
Msg-id | 20010125024522.A6906@india-today.com Whole thread Raw |
In response to | Re: Re: backend closing connections while executing... (Stephan Szabo <sszabo@megazone23.bigpanda.com>) |
Responses |
Re: Re: backend closing connections while executing...
|
List | pgsql-general |
hi .. yes i located the core file and the timestamp indicates that it has been generated around the time i was trying out the query. Can u please tell me how to generate the backtrace. Sorry not from a c background.. Anand On Wed, Jan 24, 2001 at 12:22:21PM -0800, Stephan Szabo wrote: > >It should mean that the backend exited with a SIGSEGV, probably a bug. >There should be a core file in your database directory. Can you get >a backtrace from it? > >On Thu, 25 Jan 2001, Anand Raman wrote: > >> hi guys >> on looking at the postgres log i could find this information too >> >> DEBUG: Data Base System is in production state at Wed Jan 24 20:20:26 2001 >> Server process (pid 22751) exited with status 139 at Wed Jan 24 20:23:33 2001 >> Terminating any active server processes... >> Server processes were terminated at Wed Jan 24 20:23:33 2001 >> Reinitializing shared memory and semaphores >> DEBUG: Data Base System is starting up at Wed Jan 24 20:23:33 2001 >> DEBUG: Data Base System was interrupted being in production at Wed Jan 24 20:20:26 2001 >> DEBUG: Data Base System is in production state at Wed Jan 24 20:23:33 2001 >> The Data Base System is starting up >> >> >> What is status 139 and how can i avoid it.. >> >> >> Thanks for any help >> Anand >> >> On Thu, Jan 25, 2001 at 01:06:01AM +0530, Anand Raman wrote: >> >hi guys >> > >> >While executing a simple query my the psql session reports that the >> >session has closed abnormally.. >> > >> >Can any one point out why .. The sample sql query is as follows.. >> > >> >arttoday=# select >> >arttoday-# art1.name, >> >arttoday-# CASE WHEN exh.title IS NULL THEN 'Untitled' ELSE exh.title END, >> >arttoday-# ltrim(to_char(exh_dist.length,'9999D99')) || >> >arttoday-# CASE WHEN exh_dist.breadth IS NOT NULL >> >arttoday-# THEN ' x '||ltrim(to_char(exh_dist.breadth,'9999D00'))||' cms.' >> >arttoday-# ELSE ' cms '||exh_dist.dimensional_aspect END >> >arttoday-# from >> >arttoday-# exhibit_distributions exh_dist, >> >arttoday-# exhibits exh, >> >arttoday-# artists art1 >> >arttoday-# where >> >arttoday-# exh_dist.gallery_id = 21 >> >arttoday-# and exh_dist.exhibit_id = exh.exhibit_id >> >arttoday-# and exh.artist_id2 IS NULL >> >arttoday-# and exh.artist_id1 = art1.artist_id; >> >pqReadData() -- backend closed the channel unexpectedly. >> >This probably means the backend terminated abnormally >> >before or while processing the request. >> >The connection to the server was lost. Attempting reset: >> >Succeeded. >> > >> >I am running postgresql 702 on Redhat.. >> > >> >I use the following command line parameters to start the db >> >pg_ctl -o '-i -B 100 -N 50 -o "-C -F -S4096"' start 1>postmaster.log 2>&1 >> > >> >The tables are fairly small with 600 odd rows .. >> > >> >Also when i do a query as simple as >> >arttoday=# select ltrim(to_char(exh_dist.length,'9999D99')) from exhibit_distributions exh_dist >> >the backend closes abnormally.. >> > >> >Can any help me out of this .. >> > >> >Thanks >> >Anand >>
pgsql-general by date: