Re: pg and transactions

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: pginfo <pginfo(at)t1(dot)unisoftbg(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg and transactions
Date: 2002-12-28 19:13:26
Message-ID: 20021228191326.GA10551@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Dec 28, 2002 at 16:13:17 +0100,
pginfo <pginfo(at)t1(dot)unisoftbg(dot)com> wrote:
>
> Actualy I use the table as a simple counter for unique values and I
> expect that Connection2 will wait until Connection1 finish the task.
> Is it normal for pg to work so with transactions?
> If yes how can I lock all the tables after beginning the transaction?
> If no where can I make mistake?

If you just want a unique value use sequences. They will be faster.

You didn't provide the exact commands you used in your test. Without
seeing them it is hard to tell what you might have done wrong.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-12-28 21:26:51 Re: 7.3.1: test select_having ... FAILED
Previous Message Artur Rataj 2002-12-28 16:50:41 Boolean product of rows in multiple tables