From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SERIALIZABLE with parallel query |
Date: | 2017-02-15 09:30:18 |
Message-ID: | CAEepm=1n2FqkB6UCRXx3nba-ZZzXEpZDS5uun=JBxQKGG=WQcg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 9, 2016 at 12:34 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Tue, Nov 8, 2016 at 1:51 PM, Thomas Munro
> <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
>> Currently we don't generate parallel plans in SERIALIZABLE. What
>> problems need to be solved to be able to do that?
>
> FWIW, parallel CREATE INDEX works at SERIALIZABLE isolation level by
> specially asking the parallel infrastructure to not care. I think that
> this works fine, given the limited scope of the problem, but it would
> be nice to have that confirmed.
I don't see any problem with it, but it'd be nicer to get rid of the
restriction so your change isn't needed.
--
Thomas Munro
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Khandekar | 2017-02-15 09:43:28 | Re: Parallel Append implementation |
Previous Message | Thomas Munro | 2017-02-15 09:28:13 | Re: SERIALIZABLE with parallel query |