RE: COPY locking

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, coers(at)intrinsity(dot)com
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: RE: COPY locking
Date: 2001-05-10 16:05:36
Message-ID: 3705826352029646A3E91C53F7189E320165F5@sectorbase2.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vince Vielhaber 2001-05-10 16:08:43 Re: [GENERAL] Oracle to Pg tool
Previous Message Bruce Momjian 2001-05-10 15:55:36 Re: [GENERAL] Oracle to Pg tool