Hello.
I'd like to use ORDER BY in any specified order and LIMIT, OFFSET for paging
query results.
The query is FULL OUTER JOIN of two tables by field id. I think the results of
Merge Full Join
to be ordered by some combined id. And there is no need in extra Sort if I
specify ORDER BY
that
Hello.
I've encountered deadlock with first transaction updating information
field in the primary table, and second trasaction reloading secondary
table using TRUNCATE and INSERT. Here is simple example:
create table t1 ( id integer primary key, name text );
create table t2 ( id integer
system.
Tom Lane wrote:
Alexey Nalbat [EMAIL PROTECTED] writes:
Tom Lane wrote:
Your example doesn't deadlock for me ...
With default value deadlock_timeout=1000 error raises in first
transaction:
Then there's a typo in your example --- please recheck it.
--
Alexey A. Nalbat
Price
Tom Lane wrote:
Your example doesn't deadlock for me ...
Scott Marlowe wrote:
That's not a deadlock, transaction 3 is simply waiting for transaction 1
to commit or rollback.
If you run a commit or rollback on transaction 1 then transaction 3 will
then be ready to commit or rollback as
Hello.
I've encountered deadlock on postgresql 8.1. Here is the simple example.
create table t1 (
id1 integer primary key,
val1 integer
);
create table t2 (
id2 integer primary key,
id1 integer references t1 on delete cascade,
val1 integer,
val2 integer,
val3 integer
);
insert into t1
