The missing pg_get_*def functions - Mailing list pgsql-hackers

From Joel Jacobson
Subject The missing pg_get_*def functions
Date
Msg-id CAASwCXe4DdtLCT0W8DVZ7AD-K-mOmAzNygOzEkj-wvo_NEwE7Q@mail.gmail.com
Whole thread Raw
Responses Re: The missing pg_get_*def functions
List pgsql-hackers
Existing:

pg_get_constraintdef
pg_get_indexdef
pg_get_viewdef
pg_get_triggerdef
pg_get_functiondef
pg_get_ruledef

Missing:

pg_get_ts_templatedef
pg_get_ts_parserdef
pg_get_ts_configdef
pg_get_ts_dictdef
pg_get_databasedef
pg_get_namespacedef
pg_get_languagedef
pg_get_conversiondef
pg_get_castdef
pg_get_amprocdef
pg_get_operatordef
pg_get_amopdef
pg_get_opfamilydef
pg_get_opclassdef
pg_get_tabledef
pg_get_sequencedef
pg_get_typedef
pg_get_attrdef

I'm planning to implement these. Is there any reason why the remaining functions cannot be written as SQL functions instead of C? The input data to the C-functions in pg_dump.c comes from pg_catalog anyway, so I thought it would be a lot easier just to construct the definitions in SQL where you have convenient access to the pg_catalog.


pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Proposal to add --single-row to psql
Next
From: Josh Berkus
Date:
Subject: Re: Remaining beta blockers