On 3/30/17 22:57, Vitaly Burovoy wrote: > Why do you still want to leave "ADD IF NOT EXISTS" instead of using > "SET IF NOT EXISTS"? > If someone wants to follow the standard he can simply not to use "IF > NOT EXISTS" at all. Without it error should be raised.
As I tried to mention earlier, it is very difficult to implement the IF NOT EXISTS behavior here, because we need to run the commands the create the sequence before we know whether we will need it. So this is a bit different from many other ALTER TABLE commands. It could be done, but it would require some major reworking of things or a new idea of some kind. It could be done later, but I think it's not worth holding things up for that. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers