| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Vadim Mikheev <vmikheev(at)sectorbase(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | OID/XID allocation (was Re: is PG able to handle a >500 GB Database?) |
| Date: | 2001-01-22 23:05:37 |
| Message-ID: | 14627.980204737@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> What about pre-fetching of OID's. Does that still happen for every
> backend?
Only ones that actually allocate some OIDs, I think.
> What about XID's?
XIDs are wasted on a postmaster restart, but not per-backend, because
they are cached in shared memory instead of locally. I've been thinking
about changing the code so that OIDs are allocated in the same fashion.
That would mean an extra spinlock grab per OID allocation, but so what?
We grab several spinlocks per row creation already. And we could
increase the number of OIDs allocated per pg_variable file update,
which would save some time.
Haven't got round to it yet though, and I'm not sure but what Vadim
might be planning to throw out all that code anyway ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Barnard | 2001-01-22 23:14:36 | Data entry screen building utilities |
| Previous Message | Bruce Momjian | 2001-01-22 22:57:32 | Re: Re: is PG able to handle a >500 GB Database? |