On Mon, Aug 21, 2017 at 5:30 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Thinking ahead, are we going to add a new --no-objecttype switch every
> time someone wants it?
I'd personally be fine with --no-whatever for any whatever that might
be a subsidiary property of database objects. We've got
--no-security-labels, --no-tablespaces, --no-owner, and
--no-privileges already, so what's wrong with --no-comments?
(We've also got --no-publications; I think it's arguable whether that
is the same kind of thing.)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company