From: Sven R. Kunze <srkunze@mail.de>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Speeding up JSON + TSQUERY + GIN
Date: Tue, 28 Feb 2017 09:27:09 +0100
Message-ID: <cffa8be6-4e43-7399-2f7a-5686f65acda2@mail.de> (raw)
In-Reply-To: <CAMkU=1xyf5ypGew=cgFuczQHqtc59J1CTf2EugF0hwSWu65ZCA@mail.gmail.com>
References: <2260e4e6-89ae-90dc-278c-81243b3c3510@mail.de>
<CAMkU=1xyf5ypGew=cgFuczQHqtc59J1CTf2EugF0hwSWu65ZCA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 27.02.2017 19:22, Jeff Janes wrote:
> If by 'permanently', you mean even when you intentionally break
> things, then no. You will always be able to intentionally break
> things. There is on-going discussion of an auto-prewarm feature. But
> that doesn't yet exist; and once it does, a super user will always be
> able to break it.
>
> Presumably you have a use-case in mind other than intentional sabotage
> of your caches by root. But, what is it? If you reboot the server
> frequently, maybe you can just throw 'select pg_prewarm...' into an
> init script?
I didn't express myself well enough. pg_prewarm doesn't help to speed up
those queries at all.
Looking at these numbers, I wonder why it takes ~5 secs to answer?
Best,
Sven
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: srkunze@mail.de, jeff.janes@gmail.com
Subject: Re: Speeding up JSON + TSQUERY + GIN
In-Reply-To: <cffa8be6-4e43-7399-2f7a-5686f65acda2@mail.de>
* 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