On Mon, Feb 16, 2004 at 10:16:39AM -0800, John Li wrote:
> I just implemented eRServer for one of my clients and found many problems
> with it.
Yep. There's a list dedicated to it, by the way, available through
the gborg site.
> 1. It crashes when using ?ers_addtable? to add big tables. The problem is
> that it used pg_dump ?d then tried to read the whole output in memory. I
> fixed it by reading one row at a time and inserting it to slave.
The setup scripts are pretty buggy.
> 3. There was no index created on ?_ers_uniq? on slave side. It took minutes
> per transaction to delete on huge tables. After I found the problem and
> created index on the column, it only took about 5 milliseconds to delete.
This is a new report. Thanks.
> Hope those will be fixed in the next version. I can also provide my fixes if
> needed.
I'm interested in seeing patches, for sure. I'll be applying some
things this weekend, so I'll test for the cases you mention and hit
you up for patches once I'm done.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
This work was visionary and imaginative, and goes to show that visionary
and imaginative work need not end up well. --Dennis Ritchie
