ut should users really go for the social networking features, and
start hammering away at profiles with comments and updates; I'd like
to know that the database can survive.
On 5/4/06, Jim C. Nasby <[EMAIL PROTECTED]> wrote:
On Sun, Apr 30, 2006 at 12:32:53PM -0700, Tony Lausin wrote:
&
biggest concern
with PostgreSQL. I haven't previously used autovacuum.
Regards,
Anthony
On 5/4/06, Jim C. Nasby <[EMAIL PROTECTED]> wrote:
On Sun, Apr 30, 2006 at 12:32:53PM -0700, Tony Lausin wrote:
> >[ rotfl... ] MySQL will fall over under any heavy concurrent-write
> &g
And from reading that page, one can see that InnoDB tables are still
considered to be kind of the "red headed step child" of table handlers
by the mysql crew. Sad, because it's the only table handler they have
than can truly handle any real concurrency of reads and writes mixed
together (it's a t
Thanks for the suggestions, everyone. This is what I have so far:
I require an open source DBMS because I want to avoid being locked
into a particular vendor, especially one that will send me a big bill.
That leaves me with MySQL, PostgreSQL (my preference), Firebird, and
possibly Berkeley DB (if
. I am financing this myself. hence the
apprehension about the cost. Is there another contender I should think
about.
On 4/30/06, Matthew T. O'Connor wrote:
Tony Lausin wrote:
>> [ rotfl... ] MySQL will fall over under any heavy concurrent-write
>> scenario. It's concei
In my opinion, postgresql is not the way to go when building a cMS
simply because of the way it handles strings.
A CMS should be language/region agnostic i.e. supporting any chosen
locale subset, rather then just one locale, as postgresql does. You
can throw UTF-8 at the problem and it will enabl
Very odd. I had always heard that MySql (at least originally) was a
"quick and dirty" database, easy to use, not fully standards compliant,
and not enterprise grade. Postgresql on the other hand was always
the heavyweight, standards compliant, enterprise db, which was more
difficult to use and s
[ rotfl... ] MySQL will fall over under any heavy concurrent-write
scenario. It's conceivable that PG won't do what you need either,
but if not I'm afraid you're going to be forced into Oracle or one
of the other serious-money DBs.
regards, tom lane
Hi Tom,
That's a s
Hello all,
I'm working on a CMS which requires an open source database capable of
handling hundreds of thousands of users simultaneously, with a high
rate of database writes, and without buckling. We're talking somewhere
between nerve.com/catch27.com and xanga.com/friendster.com
PostgreSQL is a
