Re: improve performance of pg_dump with many sequences

Nathan Bossart <nathandbossart@gmail.com> writes:
> Hm.  That makes sense, but both try_table_open and try_index_open error for
> wrong relkinds.  I could change all of the try_*_open functions to return
> NULL in that case, or I could just open-code the relkind check in
> pg_get_sequence_data after try_relation_open (and have it return NULL for
> non-sequences).  I'm leaning towards the latter, if for no other reason
> than it might be slightly nicer for back-patching (e.g., smaller, no new
> extern functions).

WFM.

            regards, tom lane