Hi,
On 2022-04-06 17:01:17 -0700, David G. Johnston wrote:
> On Wed, Apr 6, 2022 at 4:12 PM Andres Freund <andres@anarazel.de> wrote:
>
> The fact there is just the one outlier here suggests that this is indeed the
> better option.
FWIW, the outlier also uses pgstat_reset(), just with a small wrapper doing
the translation from slot name to slot index.
> > What does "private" mean for you? They're exposed via pgstat.h not
> > pgstat_internal.h. But not to SQL.
> I was thinking specifically of the freedom to rename and not break
> extensions. Namely, are these truly implementation details or something
> that, while unlikely to be used by extensions, still constitute an exposed
> API? It was mainly a passing thought, I'm not looking for a crash-course
> in how all that works right now.
I doubt there are extension using these functions - and they'd have been
broken the way things were in v70, because the signature already had changed.
Generally, between major releases, we don't worry too much about changing C
APIs. Of course we try to avoid unnecessarily breaking things, particularly
when it's going to cause widespread breakage.
Greetings,
Andres Freund