Thread: logical decoding cannot be used while in recovery 9.5

logical decoding cannot be used while in recovery 9.5

From
bala jayaram
Date:
Hi There,

we are getting this error "logical decoding cannot be used while in recovery" when using AWS DMS in one of the slave which is in logical as wal_level. AWS DMS job is not running due to the above error. After seeing the forums, we cannot use standby slave for logical decoding. Is this issue fixed? currently we are in 9.5

Thanks for the response

Regards
Bala

Re: logical decoding cannot be used while in recovery 9.5

From
bala jayaram
Date:
Hi team,

It would be great if could response on this? we are in mid of migration from Postgres9.5 to RDS of AWS using DMS

Thanks in advance,

Regards
Bala

On Wed, Jul 18, 2018 at 10:31 AM, bala jayaram <balajayaram22@gmail.com> wrote:
Hi There,

we are getting this error "logical decoding cannot be used while in recovery" when using AWS DMS in one of the slave which is in logical as wal_level. AWS DMS job is not running due to the above error. After seeing the forums, we cannot use standby slave for logical decoding. Is this issue fixed? currently we are in 9.5

Thanks for the response

Regards
Bala

Re: logical decoding cannot be used while in recovery 9.5

From
Andres Freund
Date:
Hi,

Please don't top-quote.

On 2018-07-20 07:18:28 -0400, bala jayaram wrote:
> It would be great if could response on this? we are in mid of migration
> from Postgres9.5 to RDS of AWS using DMS

This isn't free RDS / DMS support. In fact, we can only make informed
inferences on how they actually work, given they're closed source tools.


> > we are getting this error "logical decoding cannot be used while in
> > recovery" when using AWS DMS in one of the slave which is in logical as
> > wal_level. AWS DMS job is not running due to the above error. After seeing
> > the forums, we cannot use standby slave for logical decoding. Is this issue
> > fixed? currently we are in 9.5

No, logical decoding cannot be used on a standby. There's ongoing work
in changing that, but it's not yet supported.

Greetings,

Andres Freund