Re: table level locking different in 7.0?
| От | Tom Lane |
|---|---|
| Тема | Re: table level locking different in 7.0? |
| Дата | |
| Msg-id | 21049.958615065@sss.pgh.pa.us обсуждение |
| Ответ на | Re: table level locking different in 7.0? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: table level locking different in 7.0?
|
| Список | pgsql-hackers |
> Jim Mercer <jim@reptiles.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
В списке pgsql-hackers по дате отправления: