Re: [HACKERS] next XID is in shmem now... - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] next XID is in shmem now...
Date
Msg-id 199807211427.KAA28618@candle.pha.pa.us
Whole thread Raw
In response to next XID is in shmem now...  (Vadim Mikheev <vadim@krs.ru>)
List pgsql-hackers
> 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?

>
> All other LLL stuff will be #ifdef-ed...

As far as I am concerned, you don't need use #ifdef.

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

pgsql-hackers by date:

Previous
From: "Matthew N. Dodd"
Date:
Subject: Re: [HACKERS] cidr
Next
From: Nick Bastin
Date:
Subject: Re: [HACKERS] cidr