> 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

Wed, 17 May 2000 17:34:25 -0700
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM>
RE: table level locking different in 7.0? 
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
> ROW EXCLUSIVE lock is required (just like for INSERT, DELETE, UPDATE)...

OK, will fix (I have another little fix to make in copy.c anyway)

			regards, tom lane

Wed, 17 May 2000 20:41:25 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: table level locking different in 7.0? 
On Wed, May 17, 2000 at 08:41:25PM -0400, Tom Lane wrote:
> "Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
> > ROW EXCLUSIVE lock is required (just like for INSERT, DELETE, UPDATE)...
> 
> OK, will fix (I have another little fix to make in copy.c anyway)

can i get a patch relative to 7.0-release?

this is effecting a production database.

-- 
[ Jim Mercer                 jim@reptiles.org              +1 416 410-5633 ]
[          Reptilian Research -- Longer Life through Colder Blood          ]
[  Don't be fooled by cheap Finnish imitations; BSD is the One True Code.  ]

Wed, 17 May 2000 20:56:05 -0400
Jim Mercer <jim@reptiles.org>
Re: table level locking different in 7.0?