Re: Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns

On Mon, May 20, 2024 at 5:43 PM Jakub Wartak
<jakub(dot)wartak(at)enterprisedb(dot)com> wrote:
>
> On Tue, May 14, 2024 at 8:19 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> >
> > I looked at your version and wrote something that is shorter and
> > doesn't touch any existing text. Here it is.
>
> Hi Robert, you are a real tactician here - thanks for whatever
> references the original problem! :)

I like this text as well.

> Maybe just slight hint nearby
> expensive (to me indicating a just a CPU problem?):
>
> finding an OID that is still free can become expensive ->
> finding an OID that is still free can become expensive, thus
> significantly increasing INSERT/UPDATE response time.
>
> ? (this potentially makes it easier in future to pinpoint the user's
> problem to the this exact limitation; but feel free to ignore that too
> as I'm not attached to any of those versions)

Extra explicitness might be good. "Response time" seems like a
networking concept, so possibly ", in turn slowing down INSERT/UPDATE
statements." I'm inclined to commit that way in a couple days, barring
further comments.

PS: Sorry for the delay in looking at the latest messages