On Mon, Feb 25, 2019 at 1:04 PM Tom Lane <t...@sss.pgh.pa.us> wrote: > I'm getting slightly annoyed by arguments that reject a live, workable > patch in favor of pie-in-the-sky proposals. Both you and Robert seem > to be advocating solutions that don't exist and would take a very large > amount of work to create. If you think differently, let's see a patch.
ISTM that we should separate the question of whether or not the List API needs to continue to work without needing to change code in third party extensions from the question of whether or not the List API needs to be replaced whole cloth. These are not exactly independent questions, but they don't necessarily need to be discussed all at once. Andres said that he doesn't like the pg_list.h API. It's not pretty, but is it really that bad? The List implementation claims to be generic, but it's not actually that generic. It has to work as a Node. It's not quite fair to say that it's confusing without acknowledging that pg_list.h is special to query processing. -- Peter Geoghegan
