| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | coers(at)intrinsity(dot)com, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | RE: COPY locking |
| Date: | 2001-05-10 20:57:40 |
| Message-ID: | 3705826352029646A3E91C53F7189E320165FF@sectorbase2.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Wheeler | 2001-05-10 20:58:30 | Re: Custom Constraint |
| Previous Message | Zak McGregor | 2001-05-10 20:46:27 | Re: formatting a date |