| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [RFC] speed up count(*) |
| Date: | 2021-10-20 19:01:13 |
| Message-ID: | CAFBsxsFMe9FrRoAaEB1nwGy0v6fo6urtxxoMQ1E+pDxz+R2tLA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 20, 2021 at 2:41 PM Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
wrote:
> BTW you mentioned using BRIN indexes for min/max - I've been thinking
> about using BRIN indexes for ordering/sorting, which seems related. And
> I think it's actually doable, so I wonder why you concluded using BRIN
> indexes for min/max is not possible?
I just gathered it was not implemented in the planner, going by the explain
plan in the toy query I tried, and then I got the lightbulb in my head
about count(*).
--
John Naylor
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2021-10-20 19:06:01 | Re: Extending amcheck to check toast size and compression |
| Previous Message | Thomas Munro | 2021-10-20 18:55:54 | Interrupts vs signals |