Re: Tracing SQL statements per page/request - Mailing list pgsql-jdbc

From Guillaume Cottenceau
Subject Re: Tracing SQL statements per page/request
Date
Msg-id 87sksyg1iz.fsf@mnc.ch
Whole thread Raw
In response to Tracing SQL statements per page/request  (Shahaf Abileah <shahaf@redfin.com>)
Responses Re: Tracing SQL statements per page/request  (Shahaf Abileah <shahaf@redfin.com>)
List pgsql-jdbc
Shahaf Abileah <shahaf 'at' redfin.com> writes:

> If not, can someone recommend another approach?  In case it helps, we use
> hibernate as our O-R mapping so hibernate is responsible for generating most
> (not all) of our SQL queries (some are still issued by direct SQL).  Also, we

in pg is a good idea, as already suggested, but if many other
unrelated clients also access pg and thus it's difficult to
isolate the queries you're interested in, why not
hibernate.show_sql + appropriate logging on your direct SQL
layer?

--
Guillaume Cottenceau, MNC Mobile News Channel SA, an Alcatel-Lucent Company
Av. de la Gare 10, 1003 Lausanne, Switzerland - direct +41 21 317 50 36

pgsql-jdbc by date:

Previous
From: John R Pierce
Date:
Subject: Re: Tracing SQL statements per page/request
Next
From: "lakshmi devi"
Date:
Subject: jdbc connectivity with postgresql