Currently get_duplicate_l3_ha_port_bindings[1] is not postgres-compliant
because it's GROUP BY usage is not postgres-compliant: everything in the
SELECT list must be aggregated or in GROUP BY.
This change updates get_duplicate_l3_ha_port_bindings to respect
previous PostgreSQL rule.
Reviewed: https:/ /review. openstack. org/281517 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=77a9c1c0d49 faf9f799d78437f 5f1c4863629af2
Committed: https:/
Submitter: Jenkins
Branch: master
commit 77a9c1c0d49faf9 f799d78437f5f1c 4863629af2
Author: Cedric Brandily <email address hidden>
Date: Wed Feb 17 21:25:46 2016 +0100
Fix GROUP BY usage for PostgreSQL in migrations
Currently get_duplicate_ l3_ha_port_ bindings[ 1] is not postgres-compliant
because it's GROUP BY usage is not postgres-compliant: everything in the
SELECT list must be aggregated or in GROUP BY.
This change updates get_duplicate_ l3_ha_port_ bindings to respect
previous PostgreSQL rule.
[1] neutron. db.migration. alembic_ migrations. versions. mitaka. expand\
.1df244e556f5 _add_unique_ ha_router_ agent_port_ bindings
Change-Id: Ie99dd31d695ab8 9814a86e50d45ab abe53bd56fd
Closes-Bug: #1546731