Re: table level locking different in 7.0?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Mercer <jim(at)reptiles(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: table level locking different in 7.0?
Date: 2000-05-18 01:57:45
Message-ID: 21049.958615065@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Jim Mercer <jim(at)reptiles(dot)org> writes:
>> i had several concurrent processes which would do inserts via COPY and
>> queries.
>> on that system, i don't recall the COPY processes as being blocked by the
>> query processes.
>> now i'm running that app on solaris 7 with pgsql 7.0.
>> i'm finding that a big long select is blocking other processes which
>> are doing COPY's.

> Hmm. In 7.0, COPY IN acquires an exclusive lock on the target table,
> which is something I put in in a fit of paranoia. It may not really
> be necessary --- probably a regular write lock would be good enough.

OK, fix committed. Jim, if you're in a hurry for this fix, just change
AccessExclusiveLock to RowExclusiveLock at line 289 of
backend/commands/copy.c.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-05-18 02:28:39 Re: initdb and "exit_nicely"...
Previous Message Chris 2000-05-18 01:12:26 OO Patch