...and on Sat, Jul 05, 2003 at 12:24:18AM +0200, Bjoern Metzdorf used the keyboard:
> >> Afaik, your original posting said postgresql was 3 times slower than
> >> mysql and that you are going to leave this list now. This implied
> >> that you have made your decision between postgresql and mysql,
>
On Fri, Jul 04, 2003 at 05:47:27PM -0400, Tom Lane wrote:
> Andrew Sullivan <[EMAIL PROTECTED]> writes:
> > How could it be the transport affects the time for the query as
> > reported by the back end?
>
> How much data is being sent back by the query?
In this case, it's an all-aggregate query:
> Sean Chittenden <[EMAIL PROTECTED]> writes:
> > Getting the planner to pick
> > using the index to filter out data inserted in the last 3 days over
> > doing a seq scan... well, I don't know how you could do that without
> > changing the random_page_cost.
>
> This sounds a *whole* lot like a co
> > # The default values for PostgreSQL are extremely conservative and
> > # are likely far from ideal for a site's needs. Included in this
> > # configuration, however, are _suggested_ values to help aid in >
> > #
>
> This sort of narrative belongs in the SGML docs, not in a CONF file.
> In fa
Sean,
> The SGML docs aren't in the DBA's face and are way out of the way for
> DBAs rolling out a new system or who are tuning the system. SGML ==
> Developer, conf == DBA.
That's exactly my point. We cannot provide enough documentation in the CONF
file without septupling its length. IF we r
On Friday, July 4, 2003, at 07:07 AM, Brian Tarbox wrote:
We had about 40 tables in the db, with joined queries on about 8-12
tables.
A while ago a tested a moderately complex schema on MySQL, Pg, and
Oracle. I usually heavily normalize schemas and then define views as a
denormalized API, whi
Brian Tarbox kirjutas R, 04.07.2003 kell 15:27:
> I recently took a system from MySQL to Postgres. Same HW, SW, same data.
> The major operations where moderately complex queries (joins on 8 tables).
> The results we got was that Postgres was fully 3 times slower than MySql.
For each and every qu
> > The SGML docs aren't in the DBA's face and are way out of the way
> > for DBAs rolling out a new system or who are tuning the system.
> > SGML == Developer, conf == DBA.
>
> That's exactly my point. We cannot provide enough documentation in
> the CONF file without septupling its length. IF w
Sean,
> > That's exactly my point. We cannot provide enough documentation in
> > the CONF file without septupling its length. IF we remove all
> > commentary, and instead provide a pointer to the documentation, more
> > DBAs will read it.
>
> Which I don't think would happen and why I think the
The only time that I have ever seen load averages of 30 or more under
OpenBSD is when one of my scripts goes wild.However, I can say that
I am also seeing these load averages under PostgreSQL 7.3.2 after a
migration to it from MySQL.
MySQL Statistics:
Uptime: 1055352 Threads: 178 Question
10 matches
Mail list logo
