| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | 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 13:23:17 |
| Message-ID: | CAB7nPqQvXv9WL=AqayHR9-P+TxsN=e_KoDTGCZuRNyHp3VZ83w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-03-08 13:30:33 | Re: Freeze avoidance of very large table. |
| Previous Message | Craig Ringer | 2016-03-08 12:51:50 | Re: Parallel query fails on standby server |