From: | Lætitia Avrot <laetitia(dot)avrot(at)gmail(dot)com> |
---|---|
To: | Ryan Lambert <ryan(at)rustprooflabs(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Vik Fearing <vik(at)postgresfriends(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump new feature: exporting functions only. Bad or good idea ? |
Date: | 2021-03-27 20:30:14 |
Message-ID: | CAB_COdig4R8bRE_8mD=JxyCxgWY5=fk=QCcyTPtNwG+LQ31O_Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 | Content-Type | Size |
---|---|---|
pg_dump_functions_only_v0_2.patch | application/octet-stream | 7.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2021-03-27 20:32:57 | Re: non-HOT update not looking at FSM for large tuple update |
Previous Message | Joel Jacobson | 2021-03-27 20:27:51 | Idea: Avoid JOINs by using path expressions to follow FKs |