Re: [HACKERS] RE: xlog_bufmgr

2000-11-29 Thread Tom Lane
Yes, it's OK now. I'll remove #ifdef XLOG in other files soon. >> >> OK. Shall I do it, or do you want to? > If you have nothing to change in bufmgr now then I'll > do it myself today/tomorrow. OK, I didn't have any other reason to touch those files now. regards,

RE: [HACKERS] RE: xlog_bufmgr

2000-11-29 Thread Mikheev, Vadim
> > Yes, it's OK now. I'll remove #ifdef XLOG in other files soon. > > OK. Shall I do it, or do you want to? If you have nothing to change in bufmgr now then I'll do it myself today/tomorrow. Vadim

Re: [HACKERS] RE: xlog_bufmgr

2000-11-29 Thread Tom Lane
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes: > Yes, it's OK now. I'll remove #ifdef XLOG in other files soon. OK. Shall I do it, or do you want to? regards, tom lane

[HACKERS] RE: xlog_bufmgr

2000-11-29 Thread Mikheev, Vadim
> Would it be OK now to eliminate the separate xlog_bufmgr.c and > xlog_localbuf.c files, folding that code back into bufmgr.c and > localbuf.c? It's a real pain to have to make parallel updates > in two copies of that code... Yes, it's OK now. I'll remove #ifdef XLOG in other files soon. Vadim