pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tsirkin Evgeny <tsurkin@mail.jct.ac.il>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tsirkin Evgeny <tsurkin@jct.ac.il>
Cc: pgsql-admin@postgresql.org
Subject: Re: postmaster hangs
Date: Wed, 04 Jan 2006 17:50:22 +0200
Message-ID: <43BBEEBE.1030704@mail.jct.ac.il> (raw)
In-Reply-To: <2783.1136388320@sss.pgh.pa.us>
References: <Pine.GSO.4.58_heb2.09.0601041327350.7185@ketubot.jct.ac.il>
	<2783.1136388320@sss.pgh.pa.us>


sorry ,but i had to go with my job so i have killed one of the backends 
and this made the post restart.
However befor this i have done another backtrace ,the one that was hang 
in the middle of SELECT (not startup)
and got this:
#0  0xffffe410 in ?? ()
#1  0xbfffcf08 in ?? ()
#2  0x00000001 in ?? ()
#3  0x01490006 in ?? ()
#4  0x402ffffb in semop () from /lib/tls/libc.so.6
#5  0x08154d07 in PGSemaphoreLock ()
#6  0x08177ade in LWLockAcquire ()
#7  0x0816c7f2 in ReadBufferInternal ()
#8  0x08086eb0 in _bt_getbuf ()
#9  0x080882b6 in _bt_getroot ()
#10 0x0808ab62 in _bt_search ()
#11 0x0808aeca in _bt_first ()
#12 0x080894e0 in btgettuple ()
#13 0x081eba7b in FunctionCall2 ()
#14 0x08083f86 in index_getnext ()
#15 0x081174a0 in IndexNext ()
#16 0x0811139f in ExecScan ()
#17 0x081173c8 in ExecIndexScan ()
#18 0x0810d34d in ExecProcNode ()
#19 0x0810b9ef in ExecutorRun ()
#20 0x0817f7f3 in PortalRunSelect ()
#21 0x08180507 in PortalRun ()
#22 0x0817c5b4 in exec_simple_query ()
#23 0x0817e4d3 in PostgresMain ()
#24 0x08157754 in ServerLoop ()
#25 0x08158d1e in PostmasterMain ()
#26 0x08128c21 in main ()
I did not understand from your message wheither this is a problem in pg 
or in application.
The exact version of pg is postgres (PostgreSQL) 7.4.8.
Thanks.
Tom Lane wrote:

>Tsirkin Evgeny <tsurkin@mail.jct.ac.il> writes:
>  
>
>>Today i was trying to run an old ver. of an application on test server .
>>After a while i have got the pg hangs :
>>    
>>
>
>It looks like someone is holding a critical LWLock --- hard to tell if
>it's the BufMgrLock or a per-buffer lock for a system index's metapage,
>but must be one or the other.  Try backtracing the processes that
>*aren't* hung in this particular way.  I'm not sure you'll be able to
>learn anything much given that the build doesn't have debug info, but
>you might as well try.
>
>			regards, tom lane
>  
>




view thread (7+ messages)

Message-ID: <43BBEEBE.1030704@mail.jct.ac.il>
Permalink:  ../43BBEEBE.1030704@mail.jct.ac.il/
Also on:    postgresql.org/message-id/43BBEEBE.1030704@mail.jct.ac.il

 · 

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-admin@postgresql.org
  Cc: tsurkin@mail.jct.ac.il, tgl@sss.pgh.pa.us, tsurkin@jct.ac.il
  Subject: Re: postmaster hangs
  In-Reply-To: <43BBEEBE.1030704@mail.jct.ac.il>
  References: <Pine.GSO.4.58_heb2.09.0601041327350.7185@ketubot.jct.ac.il> <2783.1136388320@sss.pgh.pa.us> <43BBEEBE.1030704@mail.jct.ac.il>

* 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