> On Fri, Apr 5, 2019 at 10:25 PM Andres Freund <and...@anarazel.de> wrote: > > A second set of limitations is around making more of tableam > optional. Right now it e.g. is not possible to have an AM that doesn't > implement insert/update/delete. Obviously an AM can just throw an error > in the relevant callbacks, but I think it'd be better if we made those > callbacks optional, and threw errors at parse-analysis time (both to > make the errors consistent, and to ensure it's consistently thrown, > rather than only when e.g. an UPDATE actually finds a row to update).
Agree, but I guess some of tableam still should be mandatory, and then I wonder where to put the live between those that are optional and those that are not. E.g. looks like it can be relatively straightforward (ignoring `create table as` and some other stuff) to make insert/update/delete optional with messages at analysis time, but for others like parallel scan related it's probably not.
0001-Optional-tableam.patch
Description: Binary data
0002-Toytable-with-missing-am.patch
Description: Binary data
