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

Поиск
Список
Период
Сортировка
От Vadim Mikheev
Тема Re: [HACKERS] next XID is in shmem now...
Дата
Msg-id 35B4C3D6.F15F4C3B@krs.ru
обсуждение исходный текст
Ответ на Re: [HACKERS] next XID is in shmem now...  (Bruce Momjian <maillist@candle.pha.pa.us>)
Ответы Re: [HACKERS] next XID is in shmem now...
Список 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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: Complexity of contrib types
Следующее
От: Vince Vielhaber
Дата:
Сообщение: Hey Linux People (OT)