Re: Slow query on a one-tuple table

From: Luís Roberto Weck <luisroberto(at)siscobra(dot)com(dot)br>
To: Igor Neyman <ineyman(at)perceptron(dot)com>
Cc: Michael Lewis <mlewis(at)entrata(dot)com>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: Slow query on a one-tuple table
Date: 2019-09-19 20:24:39
Message-ID: 18ae8108-acaf-e9cc-96a9-ab20f4147f5a@siscobra.com.br
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Em 19/09/2019 17:11, Igor Neyman escreveu:
> With LIMIT 1, I get 3 shared buffers hit, pretty much always.
>
> ____________________________________________________________________________________
>
> Check if assessoria_pkey index is bloated.
>
> Regards,
> Igor Neyman
>
>

With this query[1] it shows:

current_database|schemaname|tblname   |idxname
|real_size|extra_size|extra_ratio|fillfactor|bloat_size|bloat_ratio|is_na|
----------------|----------|----------|---------------|---------|----------|-----------|----------|----------|-----------|-----|
database_name   |public    |assessoria|assessoria_pkey| 16384|        
0|        0.0|        90|       0.0| 0.0|false|

[1]https://github.com/ioguix/pgsql-bloat-estimation/blob/master/btree/btree_bloat-superuser.sql

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Adam Brusselback 2019-09-19 20:38:33 Re: Surprising benchmark count(1) vs. count(*)
Previous Message Igor Neyman 2019-09-19 20:11:11 RE: Slow query on a one-tuple table