Chris writes: > At the moment the explain output can get complicated to parse and > process, so I'm trying to think of another approach to use. > > Any suggestions are welcome :) I think the solution is using debug_print_plan (a guc variable). You can use it to get machine-readable plans in the logs and/or via a client connection depending on the client_min_messages and log_min_messages setting. regards, Andreas --
