Re: Keeping temporary tables in shared buffers

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Asim Praveen <apraveen(at)pivotal(dot)io>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, David Kimura <dkimura(at)pivotal(dot)io>
Subject: Re: Keeping temporary tables in shared buffers
Date: 2018-06-20 15:17:49
Message-ID: 20180620151749.GC7500@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 2, 2018 at 05:18:17PM -0400, Asim Praveen wrote:
> Hi Amit
>
> On Mon, May 28, 2018 at 4:25 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> >
> > This is one way, but I think there are other choices as well. We can
> > identify and flush all the dirty (local) buffers for the relation
> > being accessed parallelly. Now, once the parallel operation is
> > started, we won't allow performing any write operation on them. It
>
> We talked about this in person in Ottawa and it was great meeting you!
> To summarize, the above proposal to continue using local buffers for
> temp tables is a step forward, however, it enables only certain kinds
> of queries to be parallelized for temp tables. E.g. queries changing
> a temp table in any way cannot be parallelized due to the restriction
> of no writes during parallel operation.

Should this be a TODO item?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-06-20 15:20:49 Re: PATCH: backtraces for error messages
Previous Message Bruce Momjian 2018-06-20 15:13:49 Re: add default parallel query to v10 release notes? (Re: [PERFORM] performance drop after upgrade (9.6 > 10))