Re: Don't allocate IndexAmRoutine dynamically? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Don't allocate IndexAmRoutine dynamically?
Date
Msg-id 11288.1561493717@sss.pgh.pa.us
Whole thread Raw
In response to Don't allocate IndexAmRoutine dynamically?  (Andres Freund <andres@anarazel.de>)
Responses Re: Don't allocate IndexAmRoutine dynamically?
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> I think it might be worthwhile require that IndexAmRoutine returned by
> amhandler are allocated statically.

+1.  Could only be an issue if somebody were tempted to have time-varying
entries in them, but it's hard to see why that could be a good idea.

Should we enforce this for *all* handler objects?  If only index AMs,
why only them?

> It seems to me like there's not that many index AMs out there, so
> changing the signature of amhandler() to require returning a const
> pointer to a const object ought to both be enough of a warning, and not
> too big a burden.

One too many "consts" there.  Pointer to const object seems fine.
The other part is either meaningless or will cause problems.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: sigmod article about ANSI SQL 2016 features
Next
From: Tomas Vondra
Date:
Subject: Re: [PATCH] Incremental sort (was: PoC: Partial sort)