| From: | "Sven R(dot) Kunze" <srkunze(at)mail(dot)de> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Speeding up JSON + TSQUERY + GIN |
| Date: | 2017-02-28 08:27:09 |
| Message-ID: | cffa8be6-4e43-7399-2f7a-5686f65acda2@mail.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2017-02-28 16:49:42 | Re: Speeding up JSON + TSQUERY + GIN |
| Previous Message | Jeff Janes | 2017-02-27 18:22:25 | Re: Speeding up JSON + TSQUERY + GIN |