| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | jamest(at)math(dot)ksu(dot)edu (James Thompson) |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org, vadim(at)sable(dot)krasnoyarsk(dot)su (Vadim B(dot) Mikheev) |
| Subject: | Re: [HACKERS] What unresolved issues are in CVS? |
| Date: | 1999-03-11 17:18:43 |
| Message-ID: | 199903111718.MAA18339@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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.
The only thing I know of is that the new MVCC code doesn't vacuum
properly yet. It does vacuum, I just suspect is does not know how to
prevent vacuuming of rows that are being viewed by other backends.
Perhaps Vadim can comment on that.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Thompson | 1999-03-11 17:28:27 | Re: [HACKERS] What unresolved issues are in CVS? |
| Previous Message | James Thompson | 1999-03-11 16:32:32 | What unresolved issues are in CVS? |