ll need to be retrieved based on the current index
> leaf page, for example. Looking ahead across leaf page boundaries would
> be harder.
>
I also think that having effective_io_concurrency for other nodes that
bitmap scan would be really great, but for now
having a per-tablespace effect
rate 2000 WAL per hour, you should
configure it to something like 170 (or 5 min average if 2000 is a
spike). It'll perform less checkpoint and also generate less WALs.
--
Julien Rouhaud
http://dalibo.com - http://dalibo.org
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
s
performed. Was it using psql, pgAdmin or something else ?
--
Julien Rouhaud
http://dalibo.com - http://dalibo.org
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
On Thu, Sep 28, 2017 at 10:19 AM, Subramaniam C
wrote:
> Hi
>
> When I try to execute the query from sql command line then that query is
> taking only around 1 sec. But when I execute the query using JDBC(Java)
> using preparedStatement then the same query is taking around 10 secs.
>
> Can you ple
On Thu, Sep 28, 2017 at 10:58 AM, Subramaniam C
wrote:
> I configured cursor_tuple_fraction to 1 but still I am facing the same
> issue.
Can you show explain (analyze, buffers) of the query when run from
psql and run from application (you can use auto_explain for that if
needed, see https://www.p
On Tue, Oct 31, 2017 at 8:25 PM, Alexandre de Arruda Paes
wrote:
> I will be very happy with a tool(or a stats table) that shows the most
> searched values from a table(since a statistic reset). i.e.:
>
> table foo (id int, year int)
>
> top 3 searched value for year field: 2017(500x), 2016(300x)
