From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Fix bogus handling of bad strategy number in GIST consistent() f |
Date: | 2014-04-14 15:18:55 |
Message-ID: | E1WZiet-0002jB-Ft@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Fix bogus handling of bad strategy number in GIST consistent() functions.
Make sure we throw an error instead of silently doing the wrong thing when
fed a strategy number we don't recognize. Also, in the places that did
already throw an error, spell the error message in a way more consistent
with our message style guidelines.
Per report from Paul Jones. Although this is a bug, it won't occur unless
a superuser tries to do something he shouldn't, so it doesn't seem worth
back-patching.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/4dfb065b3ab662dcc96d07ee7fc9dadf6975a0cb
Modified Files
--------------
src/backend/access/gist/gistproc.c | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-04-14 16:48:35 | pgsql: doc: Update yet another place that didn't get the memo about mat |
Previous Message | Robert Haas | 2014-04-14 14:53:20 | pgsql: Correct description of constraint_name in ALTER TABLE documentat |