| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution. |
| Date: | 2016-02-22 15:07:37 |
| Message-ID: | 11434.1456153657@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> ... However, this is one of the big problems that
>> we'd have to have a solution for before we ever consider allowing
>> read-write parallelism.
> Having such a blocker for read-write parallelism would be unfortunate,
> though perhaps there isn't much help for it, and having read-only query
> parallelism is certainly far better than nothing.
IIUC, this is not the only large problem standing between us and
read-write parallelism, and probably not even the biggest one.
So I'm basically just asking that it gets documented while it's
fresh in mind, rather than leaving it for some future hackers to
rediscover the hard way. (Wouldn't be bad to doc the other known
stumbling blocks, too.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-02-22 16:21:17 | pgsql: Remove redundant PGPROC.lockGroupLeaderIdentifier field. |
| Previous Message | Stephen Frost | 2016-02-22 15:01:59 | Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2016-02-22 15:08:23 | Re: psql metaqueries with \gexec |
| Previous Message | Tom Lane | 2016-02-22 15:03:51 | Re: postgres_fdw vs. force_parallel_mode on ppc |