| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Zero throughput on a query on a very large table. |
| Date: | 2019-01-25 06:55:31 |
| Message-ID: | CAKJS1f-M23Geckc_1sycpPL5F6KfYhEqR8wNZYUcEtg0VcqLZQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, 25 Jan 2019 at 19:24, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> PS: On the third hand, you mention having created new indexes on this
> table with apparently not a lot of pain, which is a tad surprising
> if you don't have the patience to wait for a sort to finish. How
> long did those index builds take?
It would certainly be good to look at psql's \d tmp_outpatient_rev
output to ensure that the index is not marked as INVALID.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Saurabh Nanda | 2019-01-25 07:17:31 | Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? |
| Previous Message | Tom Lane | 2019-01-25 06:24:45 | Re: Zero throughput on a query on a very large table. |