| From: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com> |
| Subject: | Re: Track in pg_replication_slots the reason why slots conflict? |
| Date: | 2024-01-01 03:44:43 |
| Message-ID: | CAJpy0uA7zD9r_OnXMvhkPwerpbiQFk01ubKKWN6T_H2HpByN7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 29, 2023 at 3:35 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Fri, Dec 29, 2023 at 09:20:52AM +0530, Amit Kapila wrote:
> > Does anyone have a preference for a column name? The options on the
> > table are conflict_cause, conflicting_cause, conflict_reason. Any
> > others? I was checking docs for similar usage and found
> > "pg_event_trigger_table_rewrite_reason" function, so based on that we
> > can even go with conflict_reason.
>
> "conflict_reason" sounds like the natural choice here.
Do we have more comments on the patch apart from column_name?
thanks
Shveta
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shubham Khanna | 2024-01-01 04:36:45 | Re: Commitfest manager January 2024 |
| Previous Message | vignesh C | 2024-01-01 03:35:27 | Re: Commitfest manager January 2024 |