Re: problem with from_collapse_limit and joined views

From: Markus Schulz <msc(at)antzsystem(dot)de>
To: pgsql-performance(at)postgresql(dot)org
Cc: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Subject: Re: problem with from_collapse_limit and joined views
Date: 2010-12-04 18:20:28
Message-ID: 201012041920.29616@Mail-Followup-To
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Am Samstag 04 Dezember 2010 schrieb Kevin Grittner:
> One option would be to create a different user for running queries
> which read from complex views such as this.
>
> postgres=# create user bob;
> CREATE ROLE
> postgres=# alter user bob set from_collapse_limit = 40;
> ALTER ROLE
> postgres=# alter user bob set join_collapse_limit = 40;
> ALTER ROLE
>
> Log in as bob, and your queries should run fine.

thanks, that was really an option for us to use a different user for
creating the reports.

> Nothing leapt out at me as an issue in your postgresql.conf except:
>
> max_prepared_transactions = 20
>
> Do you actually use prepared transactions? (Sometimes people confuse
> this with prepared statements, which are a completely different
> feature.)

yes, they are needed for our JPA-based j2ee application.

regards
msc

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Markus Schulz 2010-12-04 18:46:21 Re: problem with from_collapse_limit and joined views
Previous Message Tom Lane 2010-12-04 16:59:58 Re: problem with from_collapse_limit and joined views