>> Urk... this seems pretty undesirable. > > OK, but please say what behaviour you would like in its place. > > Or are you saying you dislike this so much that you would prefer not to > be able to run ALTER TABLE concurrently?
Personally, yes. I work mostly with small databases where ease of management is a lot more important than increased concurrency, and "constraints almost always have unique names but you're not allowed to rely on that in any queries or code because there is this one wierd case that you probably will never hit where it might not be true" doesn't sound like ease of management to me. However, I hope we're not forced into that choice, because this sounds like a great feature otherwise. ....Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
