> 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 list prefers in terms of info to be ab
John Buckman wrote:
> > 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 list
> 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 list prefers to work on things, which
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 ...
regards, tom lane
---(end of broadcas
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
