From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | tony <tony(at)tgds(dot)net> |
Cc: | postgres list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: [Fwd: [webmaster] in Search of free hosting with |
Date: | 2005-04-05 13:38:19 |
Message-ID: | 1112708299.26170.283.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, 2005-04-03 at 07:43, tony wrote:
> Le dimanche 03 avril 2005 à 04:10 -0700, Jaqui Greenlees a écrit :
> > Sim Zacks wrote:
> > > dot geeks home page
> > > " The new server will *not support PostgreSQL* so please migrate your DB
> > > to MySQL (using the mygeek area of the site) or SQLite. "
> > > Why they would switch from Postgres to MySQL and not allow the postgres
> > > anymore is beyond me.
> > >
> >
> > maybe they feel the slight improvement in speed with mysql is worth
> > removing the postgrsql support.
> > mysql is slightly faster in most cases, but it's enterprise class uses
> > are usually slower. also it slows down drastically with larger db sizes.
>
> The message is dated November 18, 2004, 1:06 am... This is six month old
> news.
>
> And MySQL is faster _IF_ your site has no traffic. Once you get -> 5
> concurrent accesses to the database it falls over unless you use some
> very expensive tricks (time = money)
>
The main reason for the switch was simple supply and demand... most
users wanted the ability to use my$ql... I'd guess that this is because
most php programmers are more familiar with my$ql and my$ql still holds
the edge on the number of third party apps that often get used on free
hosting services like these.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Sven Willenberger | 2005-04-05 14:05:37 | Re: pg_restore |
Previous Message | Martín Marqués | 2005-04-05 12:25:56 | Re: [HACKERS] plPHP in core? |