| From: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | 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 07:01:54 |
| Message-ID: | CAJpy0uDL+ONASqrwbzWtZUgjb=U-jyRuEdwtkwNZf6a+bU7Kjg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 1, 2024 at 9:14 AM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
>
> 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
PFA v3 after changing column name to 'conflict_reason'
thanks
Shveta
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Track-conflicting_reason-in-pg_replication_slots.patch | application/octet-stream | 13.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2024-01-01 08:22:10 | Re: Remove unneeded PGDATABASE setting from TAP tests |
| Previous Message | Pavel Stehule | 2024-01-01 06:47:21 | Re: Autonomous transactions 2023, WIP |