| From: | Ajin Cherian <itsajin(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: repeated decoding of prepared transactions |
| Date: | 2021-02-27 06:02:17 |
| Message-ID: | CAFPTHDZqEUWJYC3yKPbXwuojMzdM5Hiaj4dhFZG4gL6hawEdwA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 27 Feb, 2021, 1:59 pm Amit Kapila, <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> I have recommended above to change this name to initial_consistency_at
> because there are times when we don't export snapshot and we still set
> this like when creating slots with CRS_NOEXPORT_SNAPSHOT or when
> creating via SQL APIs. I am not sure why Ajin neither changed the
> name nor responded to that comment. What is your opinion?
>
I am fine with the name initial_consistency_at. I am also fine with not
showing this in the pg_replication_slot view and keeping this internal.
Regards,
Ajin Cherian
Fujitsu Australia
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-02-27 06:08:37 | Re: repeated decoding of prepared transactions |
| Previous Message | Amit Kapila | 2021-02-27 04:02:19 | Re: repeated decoding of prepared transactions |