On Mon, 2005-07-11 at 15:51 +0100, Simon Riggs wrote:
> On Mon, 2005-07-11 at 09:07 -0400, Ian Westmacott wrote:
> > On Mon, 2005-07-11 at 07:31, Simon Riggs wrote:
> > > The ANALYZE commands hold read locks on the tables you wish to write to.
> > > If you slow them down, you merely slow down your
On Wed, Jul 06, 2005 at 18:54:02 -0300,
Dario Pudlo <[EMAIL PROTECTED]> wrote:
> (first at all, sorry for my english)
> Hi.
>- Does "left join" restrict the order in which the planner must join
> tables? I've read about join, but i'm not sure about left join...
The left join operator is not
Hi,
We have a couple of database that are identical (one for each customer).
They are all relatively small, ranging from 100k records to 1m records.
There's only one main table with some smaller tables, a lot of indexes and some functions.
I would like to make an estimation of the performance, th
On Tue, 2005-07-12 at 03:45, Simon Riggs wrote:
> Since vacuum_cost_delay is a userset parameter, you should be able to
> SET this solely for the analyze_thread. That way we will know with more
> certainty that it is the analyze_thread that is interfering.
That is what I have been doing. In fact,
On 7/12/05, Yves Vindevogel <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We have a couple of database that are identical (one for each customer).
> They are all relatively small, ranging from 100k records to 1m records.
> There's only one main table with some smaller tables, a lot of indexes
> and some fu
>From AMD's suit against Intel. Perhaps relevant to some PG/AMD issues.
"...125. Intel has designed its compiler purposely to degrade performance when
a program
is run on an AMD platform. To achieve this, Intel designed the compiler to
compile code
along several alternate code paths. Some paths
Help! After recently migrating to Postgres 8, I've
discovered to my horror that I can't determine which
queries are poorly performing anymore because the
logging has drastically changed and no longer shows
durations for anything done through JDBC.
So I'm desperately trying to do performance tunin
I have this in my postgresql.conf file and it works fine (set the min to
whatever you want to log)
log_min_duration_statement = 3000 # -1 is disabled, in milliseconds.
Another setting that might get what you want:
#log_duration = false
uncomment and change to true.
From the docs:
(http://www
Yes, that is exactly what I want to use!
Unfortunately, it doesn't work if you access postgres
through a JDBC connection. I don't know why. I found
a posting from back in February which talks aobut this
a little:
http://archives.postgresql.org/pgsql-admin/2005-02/msg00055.php
But I can't find
we are using jdbc -- the "log_min_duration_statement = 3000 " statement
works fine for me. Looks like there's no other work around for the
bug(?). Not sure since I have no interest in logging a million
statements a day, I only want to see the poorly performing hits.
Brent Henry wrote:
Yes,
Tom Arthurs wrote:
we are using jdbc -- the "log_min_duration_statement = 3000 "
statement works fine for me. Looks like there's no other work around
for the bug(?). Not sure since I have no interest in logging a
million statements a day, I only want to see the poorly performing hits.
Do
we are using jdbc -- the "log_min_duration_statement = 3000 "
statement works fine for me. Looks like there's no other work around
for the bug(?). Not sure since I have no interest in logging a
million statements a day, I only want to see the poorly performing hits.
Doesn't it depend on wha
hmm, yea maybe -- we are using the 7.4 driver with 8.0.x db.
Dennis wrote:
Tom Arthurs wrote:
we are using jdbc -- the "log_min_duration_statement = 3000 "
statement works fine for me. Looks like there's no other work around
for the bug(?). Not sure since I have no interest in logging a
mi
We are running Postgres 8.0.2 with the 8.0.2 jdbc
driver. And yes we are using prepared statements.
I've spent hours trying to get the
'log_min_duration_statement' and 'log_duration'
options to work with no luck. I never get any
duration from the statement. I also never see 'begin'
or 'commit'
Is there a different kind of 'prepared' statements
that we should be using in the driver to get logging
to work properly? What is the 'new' protocol?
The 8.0.2 jdbc driver uses real prepared statements instead of faked
ones. The problem is the new protocol (that the 8.0.2 driver users) has
a
Here's the answer for you from the jdbc list:
Alvin Hung wrote:
Currently, 8.0.2 / JDBC 8.0-310, log_min_duration_statement does not
work with JDBC. Nothing will get logged. This makes it very
difficult to tune a java application. Can you tell me when will this
be fixed? Thanks.
This i
2005/7/12, Mohan, Ross <[EMAIL PROTECTED]>:
> From AMD's suit against Intel. Perhaps relevant to some PG/AMD issues.
Postgres is compiled with gnu compiler. Isn't it ?
I don't know how much can Postgres benefit from an optimized Intel compiler.
--
Jean-Max Reymond
CKR Solutions Open Source
Nice
17 matches
Mail list logo
