Re: Backpatch b61d161c14 (Introduce vacuum errcontext ...) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Backpatch b61d161c14 (Introduce vacuum errcontext ...)
Date
Msg-id 2125633.1592885680@sss.pgh.pa.us
Whole thread Raw
In response to Re: Backpatch b61d161c14 (Introduce vacuum errcontext ...)  (Andres Freund <andres@anarazel.de>)
Responses Re: Backpatch b61d161c14 (Introduce vacuum errcontext ...)
Re: Backpatch b61d161c14 (Introduce vacuum errcontext ...)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> I am only suggesting that where you save the old location, as currently
> done with LVRelStats olderrinfo, you instead use a more specific
> type. Not that you should pass that anywhere (except for
> update_vacuum_error_info).

As things currently stand, I don't think we need another struct
type at all.  ISTM we should hard-wire the handling of indname
as I suggested above.  Then there are only two fields to be dealt
with, and we could just as well save them in simple local variables.

If there's a clear future path to needing to save/restore more
fields, then maybe another struct type would be useful ... but
right now the struct type declaration itself would take more
lines of code than it would save.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Global snapshots
Next
From: Amit Kapila
Date:
Subject: Re: Transactions involving multiple postgres foreign servers, take 2