-Original Message-
From: Josh Berkus [mailto:[EMAIL PROTECTED]
Sent: 28 April 2005 04:09
To: Dave Page
Cc: Joshua D. Drake; Joel Fradkin; PostgreSQL Perform
Subject: Re: [PERFORM] Final decision
Dave, folks,
Err, yes. But that's not quite the same as core telling us
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Joel
FradkinSent: Wednesday, April 27, 2005 9:02 AMTo:
PostgreSQL PerformSubject: [PERFORM] Final
decision
I spent a great deal of time over
the past week looking seriously at
Sorry I am using Redhat AS4 and postgres
8.0.2
Joel
You didnt tell us what OS
are you using, windows?
If you want good
performance you must install unix on that machine,
---
I did have a question if any folks are using two servers one for
reporting and one for data entry what system should be the beefier?
Yeah. We started putting up slaves for reporting purposes and
application specific areas using Slony replicating partial data sets to
various locations -- some
Joel,
So I am planning on sticking with postgres fro our production database
(going live this weekend).
Glad to have you.
I did not find any resolutions to my issues with Commandprompt.com (we only
worked together 2.5 hours).
BTW, your performance troubleshooting will continue to be
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Josh Berkus
Sent: 27 April 2005 17:14
To: Joel Fradkin
Cc: PostgreSQL Perform
Subject: Re: [PERFORM] Final decision
Actually, I think the problem may be ODBC. Our ODBC driver
Dave,
Actually, I think the problem may be ODBC. Our ODBC driver
is not the best
and is currently being re-built from scratch.
It is? No-one told the developers...
Regards, Dave
[and yes, I know Joshua said Command Prompt are rewriting /their/
driver]
OK. Well, let's put it this
Joel Fradkin wrote:
I spent a great deal of time over the past week looking seriously at
Postgres and MYSQL.
Objectively I am not seeing that much of an improvement in speed with
MYSQL, and we have a huge investment in postgrs.
So I am planning on sticking with postgres fro our production database
BTW, your performance troubleshooting will continue to be hampered if you
can't share actual queries and data structure. I strongly suggest that you
make a confidentiality contract with a support provider so that you can
give them detailed (rather than general) problem reports.
I am glad to
Just realize, you probably *don't* want to set that in postgresql.conf.
You just want to issue an SET enable_seqscan TO off before issuing one
of the queries that are mis-planned.
I believe all the tested queries (90 some odd views) saw an improvement.
I will however take the time to verify this
Joshua,
This article was in July 2002, so is there update to this information?
When will a new ODBC driver be available for testing? Is there a release
of the ODBC driver with better performance than 7.0.3.0200 for a 7.4.x
database?
Steve Poe
We have mentioned it on the list.
Joel Fradkin wrote:
...
I am guessing our app is like 75% data entry and 25% reporting, but the
reporting is taking the toll SQL wise.
This was from my insert test with 15 users.
Test type: Dynamic
Simultaneous browser connections: 15
Warm up time (secs): 0
Test duration: 00:00:03:13
Test
-Original Message-
From: Joshua D. Drake [mailto:[EMAIL PROTECTED]
Sent: 27 April 2005 17:46
To: Dave Page
Cc: Josh Berkus; Joel Fradkin; PostgreSQL Perform
Subject: Re: [PERFORM] Final decision
It is? No-one told the developers...
We have mentioned it on the list.
Err
Dave, folks,
Err, yes. But that's not quite the same as core telling us the current
driver is being replaced.
Sorry, I spoke off the cuff.I also was unaware that work on the current
driver had renewed. Us Core people are not omnicient, believe it or don't.
Mind you, having 2 different
On Wed, Apr 27, 2005 at 08:09:27PM -0700, Josh Berkus wrote:
Mind you, having 2 different teams working on two different ODBC drivers is a
problem for another list ...
Only two? I thought another commercial entity was also working on their
own ODBC driver, so there may be three of them.
--
Mind you, having 2 different teams working on two different ODBC drivers is a
problem for another list ...
Only two? I thought another commercial entity was also working on their
own ODBC driver, so there may be three of them.
Well I only know of one company actually working on ODBC actively
Dave Page wrote:
-Original Message-
From: Joshua D. Drake [mailto:[EMAIL PROTECTED]
Sent: 27 April 2005 17:46
To: Dave Page
Cc: Josh Berkus; Joel Fradkin; PostgreSQL Perform
Subject: Re: [PERFORM] Final decision
It is? No-one told the developers...
We have mentioned it on the list
Joshua D. Drake wrote:
Mind you, having 2 different teams working on two different ODBC drivers is
a
problem for another list ...
Only two? I thought another commercial entity was also working on their
own ODBC driver, so there may be three of them.
Well I only know of one
Joshua D. Drake wrote:
Dave Page wrote:
-Original Message-
From: Joshua D. Drake [mailto:[EMAIL PROTECTED]
Sent: 27 April 2005 17:46
To: Dave Page
Cc: Josh Berkus; Joel Fradkin; PostgreSQL Perform
Subject: Re: [PERFORM] Final decision
It is? No-one told
19 matches
Mail list logo
