RE: COPY locking - Mailing list pgsql-general

From Mikheev, Vadim
Subject RE: COPY locking
Date
Msg-id 3705826352029646A3E91C53F7189E320165FF@sectorbase2.sectorbase.com
Whole thread Raw
In response to COPY locking  (John Coers <coers@intrinsity.com>)
List pgsql-general
> > 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.
>
> See later message about eliminating lseeks --- I think we should be
> able to avoid doing this lock for every single tuple, as it does now,
> and only do it when we need to allocate a new page.

Please test current/your hio.c versions when multiple users
insert records into the same table.

Vadim

pgsql-general by date:

Previous
From: John Coers
Date:
Subject: Re: COPY locking
Next
From: David Wheeler
Date:
Subject: Re: Custom Constraint