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

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: vadim(at)krs(dot)ru (Vadim Mikheev)
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] next XID is in shmem now...
Date: 1998-07-21 14:27:13
Message-ID: 199807211427.KAA28618@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)candle(dot)pha(dot)pa(dot)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)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nick Bastin 1998-07-21 14:35:21 Re: [HACKERS] cidr
Previous Message Matthew N. Dodd 1998-07-21 14:00:03 Re: [HACKERS] cidr