RE: COPY locking - Mailing list pgsql-general

From Mikheev, Vadim
Subject RE: COPY locking
Date
Msg-id 3705826352029646A3E91C53F7189E320165F5@sectorbase2.sectorbase.com
Whole thread Raw
In response to COPY locking  (John Coers <coers@intrinsity.com>)
Responses Re: COPY locking  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
> Hmm ... semops?  What platform are you on, anyway, and which
> PG version?
> It sounds like you might be running with the fallback SysV-semaphore-
> based implementation of spinlocks, which is orders of magnitude more

access/heap/hio.c:RelationGetBufferForRelation() uses LockPage
(ie lmgr -> semops) to syncronize table extending. Probably we could
optimize this somehow, but allocation of new page in bufmgr is
horrible and that's why we have locks in hio.c from the beginning.

Vadim

pgsql-general by date:

Previous
From: "Ryan C. Bonham"
Date:
Subject: RE: RE: MS SQL 7.0 to PostgreSQL 7.1
Next
From: Justin Clift
Date:
Subject: Re: ER diagrams