Re: Bug in PostgreSQL locking mechanism or misunderstanding of the mechanism

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: amir baron <baron(dot)amir(at)gmail(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bug in PostgreSQL locking mechanism or misunderstanding of the mechanism
Date: 2014-03-24 13:45:37
Message-ID: CABUevEzrpgophMu3nUboPV+8pwEOeoO_AeHir63zkCUe_N+v_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Mar 24, 2014 at 1:11 PM, amir baron <baron(dot)amir(at)gmail(dot)com> wrote:

> Posted it in http://stackoverflow.com/q/22606063/1879564?sem=2
>
> My guess is that postgres has an issue with locking referenced table.
>

If you want a response, you will have much better luck posting the actual
question here so that people can read it. If you want an answer from
stackoverflow, ask there, and if you want a question from people here, ask
here.

In particular since you're making a bug report, it needs to contain the
actual issues observed. If it's a question, you should direct it at the
appropriate mailinglist rather than the bugreport list.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2014-03-24 18:37:30 Re: BUG #8354: stripped positions can generate nonzero rank in ts_rank_cd
Previous Message amir baron 2014-03-24 12:11:39 Bug in PostgreSQL locking mechanism or misunderstanding of the mechanism