My point was that:
>> slowest I am thinking where there is smoke there's fire.
is not a valid method of analysis.
---------------------------------------------------------------------------
Relaxin wrote:
> That doesn't really help anwser the question...
> The developers in our office (and myself) are also under the impression that
> PG is a very slow database.
> Also when you look thru the "performance" newsgroup, it seems to me that
> what people are saying is true.
>
> So instead of being a jerk to those of us who are a "novice" to PG, how
> about giving some concrete answers to these performance questions.
>
>
> > ebcorder@rockwellcollins.com wrote:
> >>
> >> I know when comparison tests are performed they can be tilted on these
> >> internet sites. But I see so many people declaring PostgreSQL to be the
> >> slowest I am thinking where there is smoke there's fire.
>
> "Bruce Momjian" <pgman@candle.pha.pa.us> wrote in message
> news:200604090338.k393c8G09848@candle.pha.pa.us...
> >
> > Lots of people still think Elvis is alive. :-)
> >
> > --
> > Bruce Momjian http://candle.pha.pa.us
> >
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
