On Thu, Jun 1, 2017 at 10:05 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > I dunno. What's the actual use-case, other than as a bad workaround > to a problem we should fix a different way?
Well, that's a fair point. I don't have a specific use case in mind. However, I also don't think that options for controlling what gets dumped should be subjected to extreme vetting. On the strength mostly of my own experiences trying to solve database problems in the real world, I generally think that pg_dump could benefit from significantly more options to control what gets dumped. The existing options are pretty good, but it's not that hard to run into a situation that they don't cover. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
