| From: | hvjunk <hvjunk(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | bhargav kamineni <bhargavpostgres(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Slot issues |
| Date: | 2019-02-18 08:57:06 |
| Message-ID: | CF854011-FCFC-43D8-9565-571898951BA7@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 14 Oct 2018, at 23:10 , Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> If you created the new basebackup using rsync, and didn't exclude
> pg_replication_slot, it'll have copied the slots from the primary. And
> thus needs a high enough max_replication_slots to work with them.
Thanks for pointing this out, after I’ve cleared the pg_replslot/ on the cascaded standby, it just “works” ;)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vijaykumar Jain | 2019-02-18 10:22:05 | Re: [External] Re: FDW, too long to run explain |
| Previous Message | Thomas Munro | 2019-02-18 02:34:48 | Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2 |