Thanks for that tip. I'll check it out.
On Tue, Jan 20, 2015 at 3:12 PM, Melvin Davidson
wrote:
> Since you are on 9.3. you might want to consider using PgBadger as a
> better way to get information about slow queries.
> http://sourceforge.net/projects/pgbadger/
>
>
> On Mon, Jan 19, 2015 at 6:4
Since you are on 9.3. you might want to consider using PgBadger as a better
way to get information about slow queries.
http://sourceforge.net/projects/pgbadger/
On Mon, Jan 19, 2015 at 6:41 PM, Tim Uckun wrote:
> Ok thanks. I am still on 9.3 so I'll adjust that setting.
>
> On Tue, Jan 20, 2015
Ok thanks. I am still on 9.3 so I'll adjust that setting.
On Tue, Jan 20, 2015 at 12:15 PM, Peter Geoghegan <
peter.geoghega...@gmail.com> wrote:
> On Mon, Jan 19, 2015 at 2:37 PM, Tim Uckun wrote:
> > I am trying to get some slow query information and the results from my
> query
> > are truncat
On Mon, Jan 19, 2015 at 2:37 PM, Tim Uckun wrote:
> I am trying to get some slow query information and the results from my query
> are truncated at 2047 characters. Some of my queries are very long so they
> get truncated in the select. Is there a way around this?
Yes. This is fixed in Postgre
I am trying to get some slow query information and the results from my
query are truncated at 2047 characters. Some of my queries are very long
so they get truncated in the select. Is there a way around this?
Here is my query.
WITH query_stats AS (
SELECT
query::text,
