diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2022-10-17 11:35:23 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2022-10-17 11:35:23 -0400 |
| commit | 2e3326929b0ba9f421f2ab1270c57b294c208a99 (patch) | |
| tree | 65740ac7e3315f9165900484701490418489a236 /src/backend/utils/adt/jsonfuncs.c | |
| parent | 9ebcb5ffdf3a1f49388c38ba5273370f49bf7d19 (diff) | |
| download | postgresql-2e3326929b0ba9f421f2ab1270c57b294c208a99.tar.gz postgresql-2e3326929b0ba9f421f2ab1270c57b294c208a99.zip | |
Guard against table-AM-less relations in planner.
The executor will dump core if it's asked to execute a seqscan on
a relation having no table AM, such as a view. While that shouldn't
really happen, it's possible to get there via catalog corruption,
such as a missing ON SELECT rule. It seems worth installing a defense
against that. There are multiple plausible places for such a defense,
but I picked the planner's get_relation_info().
Per discussion of bug #17646 from Kui Liu. Back-patch to v12 where
the tableam APIs were introduced; in older versions you won't get a
SIGSEGV, so it seems less pressing.
Discussion: https://postgr.es/m/17646-70c93cfa40365776@postgresql.org
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions