Re: pg_dump new feature: exporting functions only. Bad or good idea ?

On Fri, Mar 25, 2022 at 10:57 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>
> > Except succinctly
> > omitting system objects which should get its own general option.
>
pg_dump never dumps system objects, so I don't see a need for
> a switch to tell it not to.
>
>
I considered pg_class to be a system object, which was dumped under -t '*'

$ pg_dump -U postgres --schema-only -t '*' | grep 'CREATE.*pg_class'
CREATE TABLE pg_catalog.pg_class (
CREATE UNIQUE INDEX pg_class_oid_index ON pg_catalog.pg_class USING btree
(oid);
CREATE UNIQUE INDEX pg_class_relname_nsp_index ON pg_catalog.pg_class USING
btree (relname, relnamespace);
CREATE INDEX pg_class_tblspc_relfilenode_index ON pg_catalog.pg_class USING
btree (reltablespace, relfilenode);

$ psql -U postgres -c 'select version();'
version

----------------------------------------------------------------------------------------------------------------------------------
PostgreSQL 13.6 (Ubuntu 13.6-1.pgdg20.04+1) on x86_64-pc-linux-gnu,
compiled by gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, 64-bit
(1 row)

David J.