From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, ashutosh(dot)sharma(at)enterprisedb(dot)com |
Subject: | Re: Parallel query fails on standby server |
Date: | 2016-03-08 15:34:22 |
Message-ID: | CA+Tgmob3UqtC=ixLY-C_KPX_wgR2q8tMJZQbao3Ur3i=VzxWUw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 8, 2016 at 8:23 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Tue, Mar 8, 2016 at 9:51 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>> On 8 March 2016 at 20:30, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> wrote:
>>>
>>> While testing a parallel scan feature on standby server, it is found that
>>> the parallel query fails with an error "ERROR: failed to initialize
>>> transaction_read_only to 0".
>>>
>>
>> Looks like it might be a good idea to add some tests to src/test/recovery
>> for parallel query on standby servers...
>
> An even better thing would be a set of read-only tests based on the
> database "regression" generated by make check, itself run with
> pg_regress.
I'm not sure anything in the main regression suite actually goes
parallel right now, which is probably the first thing to fix.
Unless, of course, you use force_parallel_mode=regress, max_parallel_degree>0.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-03-08 15:36:51 | Odd warning from pg_dump |
Previous Message | Tom Lane | 2016-03-08 15:30:36 | Re: Exclude pg_largeobject form pg_dump |