| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Jonathan Ellis <jbe(at)familyellis(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: locking problems |
| Date: | 2002-03-18 00:14:14 |
| Message-ID: | 20020318111414.C24566@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Mar 16, 2002 at 11:42:57AM -0800, Jonathan Ellis wrote:
> I guess I don't understand locking in PG... I have a simple statement that
> is deadlocking:
>
> update minions set hp = hp_max
>
> there are no triggers or rules on this table. Even when I try
>
> lock table minions in row share mode
>
> it still deadlocks. How can a statement like this deadlock? Doesn't it
> acquire all necessary locks atomically?
Is that the only statement in the transaction?
How many rows are there in that table?
How do you know it's deadlocking?
HTH,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Ignorance continues to thrive when intelligent people choose to do
> nothing. Speaking out against censorship and ignorance is the imperative
> of all intelligent people.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Reyes | 2002-03-18 01:50:54 | Re: Maintainer(s) for gborg? |
| Previous Message | Martijn van Oosterhout | 2002-03-18 00:08:13 | Re: limit /offset |