| From: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Ajin Cherian <itsajin(at)gmail(dot)com>, Sergei Kornilov <sk(at)zsrv(dot)org>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: extensible options syntax for replication parser? |
| Date: | 2021-10-13 14:05:47 |
| Message-ID: | a432c672-e72d-3d3b-0d44-ab0169f75a77@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/5/21 10:26 PM, Robert Haas wrote:
> Hearing no further comments, I've gone ahead and committed these
> patches. I'm still slightly nervous that I may have missed some issue,
> but I think at this point having the patches in the tree is more
> likely to turn it up than any other course of action.
I have tested couple of scenarios of pg_basebackup / pg_receivewal
/pg_recvlogical / Publication(wal_level=logical) and
Subscription e.t.c against HEAD (with patches) and cross-version
testing. Things look good to me and no breakage was found.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2021-10-13 14:26:17 | Missing log message in recoveryStopsAfter() for RECOVERY_TARGET_TIME recovery target type |
| Previous Message | Robert Haas | 2021-10-13 14:03:02 | Re: should we allow users with a predefined role to access pg_backend_memory_contexts view and pg_log_backend_memory_contexts function? |