On Wed, Feb 10, 2010 at 01:12:31PM -0300, Alvaro Herrera wrote:
> What happened to this patch? Was it abandoned in favor of server-side
> tracing?
I think it was abandoned but I don't remember seeing any patch/suggestion to
improve server-side tracing. This might come from server-side tracing alr
Hans-Jürgen Schönig wrote:
> hi,
>
> this patch implements SQL side tracing / tracking of statements and
> statement execution times.
> it is primarily intended to allow programmers to gather information
> about the runtime behavior of a program and to figure out easily
> where the bottlenecks are
Michael Meskes írta:
>> this area (patch sent some time ago) and we were finally able to
>> catch up with Informix performance-wise in this area (mostly cursor
>> work). before this auto_prepare fix, we were sometimes 2-3 times
>>
>
> Which fix are you talking about? I don't really remember a
Michael Meskes writes:
> On Wed, Jan 13, 2010 at 10:30:32PM +0100, Hans-Juergen Schoenig wrote:
>> performance tune your precompiler application. in PostgreSQL it is
>> currently a little hard to get from the log what is executed how
>> often by which application in which speed and so on. so, we c
On Wed, Jan 13, 2010 at 10:30:32PM +0100, Hans-Juergen Schoenig wrote:
> performance tune your precompiler application. in PostgreSQL it is
> currently a little hard to get from the log what is executed how
> often by which application in which speed and so on. so, we came up
Hard or impossible? I
On Wed, Jan 13, 2010 at 4:42 PM, Tom Lane wrote:
> Hans-Juergen Schoenig writes:
>> Michael Meskes wrote:
>>> Before looking into it in detail I think we should first figure out if this
>>> feature really has a benefit.
>
>> the use cases for this thing are quite simple: we are currently porting
Hans-Juergen Schoenig writes:
> Michael Meskes wrote:
>> Before looking into it in detail I think we should first figure out if this
>> feature really has a benefit.
> the use cases for this thing are quite simple: we are currently porting
> hundreds (!) of complex Informix terminal applications
Michael Meskes wrote:
Hans,
nce Jaime already asked for a use case, just a few small comments from
me.
@@ -4,6 +4,7 @@
#include "postgres_fe.h"
#include
+#include
This is not portable. You don't want to include this header.
Did I see this right that you use the statement cache
Hans,
nce Jaime already asked for a use case, just a few small comments from
me.
> @@ -4,6 +4,7 @@
> #include "postgres_fe.h"
>
> #include
> +#include
This is not portable. You don't want to include this header.
Did I see this right that you use the statement cache for auto-prepared
stateme
2010/1/12 Hans-Jürgen Schönig :
> hi,
>
> this patch implements SQL side tracing / tracking of statements and
> statement execution times.
>
why is this better than using the "auto explain" module?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de siste
10 matches
Mail list logo
