Re: table level locking different in 7.0?
| От | Tom Lane |
|---|---|
| Тема | Re: table level locking different in 7.0? |
| Дата | |
| Msg-id | 19586.958609176@sss.pgh.pa.us обсуждение |
| Ответ на | table level locking different in 7.0? (Jim Mercer <jim@reptiles.org>) |
| Ответы |
Re: table level locking different in 7.0?
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.
(6.5's COPY code neglected to acquire any lock at all, which is surely
*not* good enough, but maybe I overreacted.)
Comments anyone?
regards, tom lane
В списке pgsql-hackers по дате отправления: