pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: samantha mahindrakar <sam.mahindrakar@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Multiple locks problem
Date: Thu, 17 Jul 2008 16:30:44 -0400
Message-ID: <f0c828c40807171330g140f08e1h73bc1add269d57b4@mail.gmail.com> (raw)

Hi....
Below is the locks that are generated by my program. Can someone thrown some
light as to why i see multiple locks on the same table?.
I first insert data in the table 'imputed_prediction' and the select data
from it..........since i see locks on indexes.........................iam
assuming its happening during the selection of data.
I havent specifically defined locks either. However i select data from the
tabel across multiple functions.I see 4 locks on the same table
imputed_prediction......i insert data,select and truncate the table finally.
Under what conditions do we see such locks???The program runs too with this
condition.

"imputed_data_helper";85150013;2880;t;"AccessShareLock"
"imputed_data_helper_i1";85150013;2880;t;"AccessShareLock"
"imputed_data_helper_i2";85150013;2880;t;"AccessShareLock"
"imputed_data_helper_i3";85150013;2880;t;"AccessShareLock"
"imputed_data_helper_i4";85150013;2880;t;"AccessShareLock"
"imputed_data_helper_pk";85150013;2880;t;"AccessShareLock"
"imputed_lane_data_07_08";85150013;2880;t;"RowExclusiveLock"
"imputed_lane_data_07_08_measurement_start_i";85150013;2880;t;"RowExclusiveLock"
"imputed_lane_data_07_08_pk";85150013;2880;t;"RowExclusiveLock"
"imputed_lane_data_07_08_quality_i";85150013;2880;t;"RowExclusiveLock"
"imputed_prediction";85162809;1900;f;"ShareUpdateExclusiveLock"
"imputed_prediction";85150013;2880;t;"AccessShareLock"
"imputed_prediction";85150013;2880;t;"RowExclusiveLock"
"imputed_prediction";85150013;2880;t;"ShareLock"
"imputed_prediction";85150013;2880;t;"AccessExclusiveLock"
"imputed_prediction_i1";85150013;2880;t;"AccessExclusiveLock"
"imputed_prediction_i1";85150013;2880;t;"AccessShareLock"
"imputed_prediction_i2";85150013;2880;t;"AccessExclusiveLock"
"imputed_prediction_i2";85150013;2880;t;"AccessShareLock"
"imputed_prediction_i3";85150013;2880;t;"AccessShareLock"
"imputed_prediction_i3";85150013;2880;t;"AccessExclusiveLock"
"imputed_prediction_i4";85150013;2880;t;"AccessExclusiveLock"
"imputed_prediction_i4";85150013;2880;t;"AccessShareLock"
"imputed_prediction_i5";85150013;2880;t;"AccessExclusiveLock"
"imputed_prediction_i5";85150013;2880;t;"AccessShareLock"


Sam

Message-ID: <f0c828c40807171330g140f08e1h73bc1add269d57b4@mail.gmail.com>
Permalink:  ../f0c828c40807171330g140f08e1h73bc1add269d57b4@mail.gmail.com/
Also on:    postgresql.org/message-id/f0c828c40807171330g140f08e1h73bc1add269d57b4@mail.gmail.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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: sam.mahindrakar@gmail.com
  Subject: Re: Multiple locks problem
  In-Reply-To: <f0c828c40807171330g140f08e1h73bc1add269d57b4@mail.gmail.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