BUG #11705: \d(escribe) table shows incorrect check constraint

Поиск
Список
Период
Сортировка
От finkel@sd-il.com
Тема BUG #11705: \d(escribe) table shows incorrect check constraint
Дата
Msg-id 20141017194258.2957.58603@wrigleys.postgresql.org
обсуждение исходный текст
Ответы Re: BUG #11705: \d(escribe) table shows incorrect check constraint
Re: BUG #11705: \d(escribe) table shows incorrect check constraint
Список pgsql-bugs
The following bug has been logged on the website:

Bug reference:      11705
Logged by:          Joel Finkel
Email address:      finkel@sd-il.com
PostgreSQL version: 9.1.13
Operating system:   x86_64-unknown-linux-gnu
Description:

We have a table with this constraint:

CONSTRAINT check_m_nullability CHECK (((m1 IS NULL) AND (m2 IS NULL)) OR
((m1 IS NOT NULL) AND (m2 IS NOT NULL)))

When we \d <table name> it is listed as:

Check constraints:
    "check_m_nullability" CHECK (m1 IS NULL AND m2 IS NULL OR m1 IS NOT NULL
AND m2 IS NOT NULL)"

The application of the constraint appears to be correct.  The problem is
that \d is dropping important parentheses in its output; so it is showing an
incorrect description.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #10680: LDAP bind password leaks to log on failed authentication
Следующее
От: chenhj
Дата:
Сообщение: 32 bit libpq fail to connecting when set a very large "connect_timeout" value