agora inbox for postgres@postgres.berkeley.edu  

help / color / mirror / Atom feed

From: Mike Doughney <mike@ss1.digex.net>
To: postgres@postgres.Berkeley.EDU
Cc: mcguire@ss1.digex.net
Cc: mike@ss1.digex.net
Subject: Timeout on deadlock
Date: Wed, 19 Oct 1994 03:20:37 -0400
Message-ID: <199410190720.AA26023@ss1.digex.net> (raw)


I've been having considerable difficulty with postgres locking up when
two programs are attempting to access the same database at the same
time.  I've written two programs, one is a batch process which is
retrieving and appending records, the other an interactive program
that performs only retrievals.  When I attempt to do interactive
retrievals at the same time the batch is running I frequently receive
these types of messages from one or the other process (and
occasionally both):

: NOTICE:Oct 19 03:06:33:Timeout -- possible deadlock
: WARN:Oct 19 03:06:33:WaitOnLock: error on wakeup - Aborting this transaction

On one occasion the batch process simply quit entirely with this
message, which I gather is from PQexec:

: Error: No response from the backend, exiting...

On one other occasion the batch process repeatedly timed out until my
program quit trying (after 5 tries) and exited; the retries continued
after the interactive program was finished.

The batch process is using a begin/end block for every input record;
each input record generates anywhere from 5 to 50 appends and a number
of retrievals.

Postgres version is 4.1 running under SunOS 4.1.3 with Kerberos
authentication.  I'm using pgperl.

Any suggestions, fixes, patches, etc. much appreciated.


==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"

   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================

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 using the --to and --cc options:
  reply via email

  To: postgres@postgres.berkeley.edu
  Cc: mike@ss1.digex.net, mcguire@ss1.digex.net
  Subject: Re: Timeout on deadlock
  In-Reply-To: <199410190720.AA26023@ss1.digex.net>

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

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