I'm currently using the CVS code as part of a project I'm working on and
have not run any any problems. Today at work, looking at my oracle
processes which look like
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND6174 oradba 23 0 33M 12M sleep 0:00
0.18% 0.12% oracle6166 oradba 33 0 35M 12M sleep 0:00 0.16% 0.11% oracle6168 oradba 33 0 33M
10Msleep 0:00 0.13% 0.08% oracle6170 oradba 33 0 33M 10M sleep 0:00 0.13% 0.08% oracle6176 oradba
27 0 33M 10M sleep 0:00 0.08% 0.05% oracle6172 oradba 33 0 33M 10M sleep 0:00 0.08% 0.05%
oracle351 oradba 33 0 11M 2944K sleep 0:00 0.03% 0.02% tnslsnr
I've started to wonder why bother with this bloated beast at all. We are
just now moving to an RDBMS and so its the perfect time to switch (Oracle
doesn't cost us a cent so no money lost). Problem is, I'd rather not go
back to 6.4.2. I'm thinking move the Oracle stuff to CVS postgresql and
just dealing with the problems if any come up. I'd hope that would
provide you guys with additional feedback and thus possibly help improve
the code base prior to 6.5.
So, are there any show stoppers in CVS postgresql. I myself haven't hit
anything, but I'm not really pounding on it yet.
->->->->->->->->->->->->->->->->->->---<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<
James Thompson 138 Cardwell Hall Manhattan, Ks 66506 785-532-0561 Kansas
State University Department of Mathematics
->->->->->->->->->->->->->->->->->->---<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<
