Re: pg_dump new feature: exporting functions only. Bad or good idea ? - Mailing list pgsql-hackers

From Lætitia Avrot
Subject Re: pg_dump new feature: exporting functions only. Bad or good idea ?
Date
Msg-id CAB_COdig4R8bRE_8mD=JxyCxgWY5=fk=QCcyTPtNwG+LQ31O_Q@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump new feature: exporting functions only. Bad or good idea ?  (Ryan Lambert <ryan@rustprooflabs.com>)
Responses Re: pg_dump new feature: exporting functions only. Bad or good idea ?  (ahsan hadi <ahsan.hadi@gmail.com>)
List pgsql-hackers

Using --functions-only along with --table=<name> does not error out and warn the user, instead it creates a dump containing only the SET commands.  An error similar to using --functions-only along with --data-only seems like a good idea.


Thank you for giving my patch a try.
I added the new if statement, so that the program will error should the `--functions-only` be used alongside the `--table` option.

The patch has been added to the next commifest.

Have a nice day,

Lætitia
Attachment

pgsql-hackers by date:

Previous
From: "Joel Jacobson"
Date:
Subject: Idea: Avoid JOINs by using path expressions to follow FKs
Next
From: Noah Misch
Date:
Subject: Re: non-HOT update not looking at FSM for large tuple update