Excerpts from Tom Lane's message of mar oct 25 14:57:43 -0300 2011: > I'm not sure if this is something we can back-patch --- I don't see any > dependencies in our own code on what names RI triggers have, but I'm > afraid there is client-side code out there that knows it.
Yeah, sounds possible. > In any case, > changing the name assignments would not fix things for existing > triggers; but if we did back-patch then any affected users could just > drop and re-create the problematic FK constraint. Or maybe we could > back-patch a change in creation order and rely on that usually working. > Given the lack of prior complaints that might be good enough. The latter looks reasonable ... particularly if the symptoms of a botched order would be immediately visible -- the user could just drop and reload the constraints to fix the order in the very unlikely case that they are reversed. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
