> As far as getting into base postgresql distro. I don't mind it rewriting but I
> have some reservations.
> 1) As it is postgresql source code is huge. Adding functions to it which
> directly taps into it's nervous system e.g. cache, would take far more time to
> perfect in all conditions.
It d
Just an FYI - this kind of thing would be a *great* feature addition to the generic
PostgresSQL release. We at Lyris often hear that "postgressql is very slow, and the
files are getting larger" and then "wow! it's so much faster now that we're regularly
vacuuming!" after we let them know about
> John Buckman <[EMAIL PROTECTED]> writes:
> > It seems that with larger database sizes (500,000 rows and larger) and
> > high stress, the server daemon has a tendency to core.
> We'd love to see some stack traces ...
Yeah, I just didn't know what form this l
> John Buckman <[EMAIL PROTECTED]> writes:
> > It seems that with larger database sizes (500,000 rows and larger) and
> > high stress, the server daemon has a tendency to core.
> We'd love to see some stack traces ...
Yeah, I just didn't know what form this lis
Hello -- I'm the lead programmer of Lyris ListManager, an email list server that run
on PostgreSQL, Oracle, and MS/SQL.
About 20% of our client base of 4000 runs on PostgresSQL -- it's very popular with our
clients -- much more than Oracle is (about 3%).
Unfortunately we have about a dozen cli
