| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Metin Doslu <metin(at)citusdata(dot)com> |
| Cc: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Parallel Select query performance and shared buffers |
| Date: | 2013-12-03 16:32:47 |
| Message-ID: | CAGTBQpYE3oRUfrt+++E-AFenfnnC8tRZie-Gf7fZHkV48Cwxyg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On Tue, Dec 3, 2013 at 1:24 PM, Metin Doslu <metin(at)citusdata(dot)com> wrote:
> Looking into syncscan.c, it says in comments:
>
> "When multiple backends run a sequential scan on the same table, we try to
> keep them synchronized to reduce the overall I/O needed."
>
> But in my workload, every process was running on a different table.
Ah, ok, so that's what you meant by "independent tables".
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Kruse | 2013-12-03 16:33:02 | Re: Time-Delayed Standbys |
| Previous Message | Tom Lane | 2013-12-03 16:30:15 | Re: pgsql: libpq: change PQconndefaults() to ignore invalid service files |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Michel | 2013-12-03 20:18:39 | Re: One query run twice in parallel results in huge performance decrease |
| Previous Message | Metin Doslu | 2013-12-03 16:24:55 | Re: Parallel Select query performance and shared buffers |