Skip site navigation (1) Skip section navigation (2)

Re: Perpetuating the myth...annoying

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: weigelt(at)metux(dot)de
Cc: postgresql advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Perpetuating the myth...annoying
Date: 2004-06-04 19:20:36
Message-ID: 40C0CB84.6050200@Yahoo.com (view raw or flat)
Thread:
Lists: pgsql-advocacy
On 6/3/2004 4:28 PM, Enrico Weigelt wrote:

> * David Costa <geeks(at)dotgeek(dot)org> wrote:
> 
> <snip>
>> I am sure SQLite can be faster, but its not comparable with either 
>> MySQL or PostgreSQL
>> so is this text based "db"  http://txtsql.sourceforge.net/
> Ah, I'll have a look at this. 
> I'm using "flat" text tables in some web applications. 
> If I can edit the txtsql database by hand, I'll probably switch to it :)
> 
> <snip>
>> When you talk about speed the average PHP developer is thinking about 
>> his guestbook or forum becoming slower with Pgsql
>> and this is not true ;)
> Well, this comes (better: *came*) from the issue that pgsql is a little 
> bit slower on connection startup than mysql (is it still ?). Some people
> say, that comes *because* mysql is MT and pgsql is MP, but IMHO this is 
> not really true. 
> 
> I already talked about this issue here. We could implement some kind
> of preforking or backends processing more then one connection subsequently.

Or we could just encourage people to use what's availabe. Pgpool has 
more advantages for PHP applications than just that anyway.


Jan


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck(at)Yahoo(dot)com #


In response to

pgsql-advocacy by date

Next:From: Josh BerkusDate: 2004-06-04 19:20:47
Subject: Re: [SQL] SQL Spec Compliance Questions
Previous:From: eleinDate: 2004-06-04 18:33:16
Subject: Re: [SQL] SQL Spec Compliance Questions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group