| From: | Joel Jacobson <joel(at)trustly(dot)com> |
|---|---|
| To: | Vik Reykja <vikreykja(at)gmail(dot)com> |
| Cc: | Michael Glaesemann <grzm(at)seespotcode(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Schema version management |
| Date: | 2012-07-05 14:35:52 |
| Message-ID: | CAASwCXdjxxX1mGya08X1x_aXm1xkLtH6dpCUMX8a15kv-aMCCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Maybe it could be made an option to pg_dump?
Some users and their systems might not even have overloaded functions,
and these users will of course prefer a nice looking filename, i.e. all
functions
having the same name kept in the same file. Which for them will mean only
one function per file anyway.
pg_dump --split --overloaded-functions-to-same-file
Other users and their systems might have a lot of overloaded functions,
like the equal() example mentioned, they will of course prefer to keep
all functions in separate files.
pg_dump --split --overloaded-functions-to-separate-files
Then, one can discuss which one should be the default option for --split,
I would prefer the same file variant, and think most other users would too,
except for users with a lot of overloaded functions.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-07-05 14:46:52 | Re: Schema version management |
| Previous Message | Vik Reykja | 2012-07-05 13:56:27 | Re: Schema version management |