From: | Önder Kalacı <onderkalaci(at)gmail(dot)com> |
---|---|
To: | "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com> |
Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher |
Date: | 2022-09-22 16:13:50 |
Message-ID: | CACawEhWc5UDgvos_OBrpZVfYdsWDJxn=cirigjzX5qc-UG2-vw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Peter, Kuroda
kuroda(dot)hayato(at)fujitsu(dot)com <kuroda(dot)hayato(at)fujitsu(dot)com>, 21 Eyl 2022 Çar,
04:21 tarihinde şunu yazdı:
> > One last thing - do you think there is any need to mention this
> > behaviour in the pgdocs, or is OK just to be a hidden performance
> > improvement?
>
> FYI - I put my opinion.
> We have following sentence in the logical-replication.sgml:
>
> ```
> ...
> If the table does not have any suitable key, then it can be set
> to replica identity <quote>full</quote>, which means the entire row
> becomes
> the key. This, however, is very inefficient and should only be used as
> a
> fallback if no other solution is possible.
> ...
> ```
>
> Here the word "very inefficient" may mean that sequential scans will be
> executed every time.
> I think some descriptions can be added around here.
>
Making a small edit in that file makes sense. I'll attach v13 in the next
email that also includes this change.
Also, do you think is this a good time for me to mark the patch "Ready for
committer" in the commit fest? Not sure when and who should change the
state, but it seems I can change. I couldn't find any documentation on how
that process should work.
Thanks!
From | Date | Subject | |
---|---|---|---|
Next Message | Önder Kalacı | 2022-09-22 16:13:54 | Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher |
Previous Message | Andres Freund | 2022-09-22 16:10:14 | Re: Summary function for pg_buffercache |