From: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
---|---|
To: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, shveta malik <shveta(dot)malik(at)gmail(dot)com> |
Subject: | Re: Issue with logical replication slot during switchover |
Date: | 2025-08-29 03:34:01 |
Message-ID: | CAJpy0uB6F+y9nLgEdA82_XD9Eappgr62akTd6X-XAREdis+2Yg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 28, 2025 at 9:11 PM Fabrice Chapuis <fabrice636861(at)gmail(dot)com> wrote:
>
> What is the procedure to create this patch. Thank you for your help.
>
We use 'git format-patch' to generate formatted patches. I have given
a few links ([1],[2],[3)] on know-how.
I usually use these steps:
git add <file1.c> <adds file to staging area>
git add <file2.c>
<once all the required files are added, create a commit>
git commit <add the required message to describe the patch>
git format-patch -1 -v1 <create the patch>
-1-> to create patch for last 1 commit
-v1 --> patch-prefix. I have used v1 which indicates version-1, when
we upload the patch a second time, we can use -v2 and so on.
[1]: https://stackoverflow.com/questions/6658313/how-can-i-generate-a-git-patch-for-a-specific-commit
[2]: https://www.geeksforgeeks.org/git/how-to-generate-a-git-patch-for-a-specific-commit/
[3]: https://gist.github.com/ganapathichidambaram/3504e31fc8ba809762b3a0d9d9ef8ec2
thanks
Shveta
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2025-08-29 03:37:10 | Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 |
Previous Message | Chao Li | 2025-08-29 03:29:15 | Re: SQL:2023 JSON simplified accessor support |