RE: table level locking different in 7.0?

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Mercer <jim(at)reptiles(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: RE: table level locking different in 7.0?
Date: 2000-05-18 00:34:25
Message-ID: 8F4C99C66D04D4118F580090272A7A23018BE7@SECTORBASE1
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.)

Oh, seems I forgot about COPY in 6.5... -:(
ROW EXCLUSIVE lock is required (just like for INSERT, DELETE, UPDATE)...

Vadim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-05-18 00:41:25 Re: table level locking different in 7.0?
Previous Message Tom Lane 2000-05-18 00:19:36 Re: table level locking different in 7.0?