Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] next XID is in shmem now...

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] next XID is in shmem now...
Date: 1998-07-21 16:37:42
Message-ID: 35B4C3D6.F15F4C3B@krs.ru (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruce Momjian wrote:
> 
> > Backends fetch 1024 XIDs now and place them in shmem.
> > There is space in VariableCache struct for OIDs as well
> > but I didn't change GetNewObjectId() due to the
> > CheckMaxObjectId() stuff... Bruce ?
> 
> What can I do to help?  Is the problem that a backend can set the next
> oid by specifiying an oid greater than the current one?

No problem - I just havn't time to think about this, sorry.

> 
> >
> > All other LLL stuff will be #ifdef-ed...
> 
> As far as I am concerned, you don't need use #ifdef.

I'm not sure how much ready/robust this will be in 6.4.
This is long-term project...

Vadim

In response to

Responses

pgsql-hackers by date

Next:From: Vince VielhaberDate: 1998-07-21 16:41:32
Subject: Hey Linux People (OT)
Previous:From: Bruce MomjianDate: 1998-07-21 16:36:08
Subject: Re: Complexity of contrib types

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group