| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Ranier Vilela <ranier_gyn(at)hotmail(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [BUG] Uninitializaed configOut.leafType used. |
| Date: | 2019-11-13 18:20:13 |
| Message-ID: | 20191113182013.3rpzaozpqisnzzps@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2019-11-13 18:11:35 +0000, Ranier Vilela wrote:
> Now we have a technical explanation, which explains the problem.
> And not a judgment about knowledge.
I have no idea what that means.
> Let's hope that always SPGIST_CONFIG_PROC hit first.
It will be. The list of support functions is is essentially ordered by
amprocnum. And the procedure numbers are:
/* SPGiST opclass support function numbers */
#define SPGIST_CONFIG_PROC 1
#define SPGIST_CHOOSE_PROC 2
#define SPGIST_PICKSPLIT_PROC 3
#define SPGIST_INNER_CONSISTENT_PROC 4
#define SPGIST_LEAF_CONSISTENT_PROC 5
#define SPGIST_COMPRESS_PROC 6
#define SPGISTNRequiredProc 5
#define SPGISTNProc 6
It certainly could be more obvious. I'm not a fan of the spgist code :(.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mukesh Chhatani | 2019-11-13 18:37:30 | Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10 |
| Previous Message | Ranier Vilela | 2019-11-13 18:11:35 | RE: [BUG] Uninitializaed configOut.leafType used. |