From: Markus Schulz <msc@antzsystem.de>
To: pgsql-performance@postgresql.org
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Subject: Re: problem with from_collapse_limit and joined views
Date: Sat, 4 Dec 2010 19:20:28 +0100
Message-ID: <201012041920.29616@Mail-Followup-To> (raw)
In-Reply-To: <4CFA09E2020000250003829C@gw.wicourts.gov>
References: <4CFA09E2020000250003829C@gw.wicourts.gov>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: msc@antzsystem.de, Kevin.Grittner@wicourts.gov
Subject: Re: problem with from_collapse_limit and joined views
In-Reply-To: <201012041920.29616@Mail-Followup-To>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox