Re: Need to backpatch 2985e16 to 9.3 and further (HS regression test out)

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Need to backpatch 2985e16 to 9.3 and further (HS regression test out)
Date: 2014-06-05 09:11:58
Message-ID: CA+HiwqHa-9zF6besXUfL+FtFJJG5CkP+YJAGPRp43U2kB7tAKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 5, 2014 at 5:37 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On 2014-06-05 16:56:08 +0900, Amit Langote wrote:
>> On Thu, Jun 5, 2014 at 4:09 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> > Do we need to back-patch this to older versions (i,e. 9.2, 9.1, ..)?
>> >
>>
>> Yes, this should be backpatched to 9.2, 9.1, 9.0, too.
>
> I don't think it really needs to go to 9.0 - that didn't have
> serializable. And before that it was fine to use serializable on a HS
> standby.
>

Yeah, you are right, s 9.0 hot standby server does allow to -

[amit(at)localhost git]$ psql postgres -p 15432
Timing is on.
psql (9.0.17)
postgres=# begin transaction isolation level serializable;
BEGIN

whereas -

[amit(at)localhost git]$ psql postgres -p 15432
Timing is on.
psql (9.1.13)
Type "help" for help.

postgres=# begin transaction isolation level serializable;
ERROR: cannot use serializable mode in a hot standby
HINT: You can use REPEATABLE READ instead.

Perhaps just the s/VACUUM/ANALYZE part for 9.0 then

--
Amit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-06-05 09:59:31 Re: doPickSplit stack buffer overflow in XLogInsert?
Previous Message Michael Paquier 2014-06-05 09:06:42 Re: slotname vs slot_name