pgsql: Revert patch to coerce 'unknown' type parameters in the backend.

Поиск
Список
Период
Сортировка
От heikki@postgresql.org (Heikki Linnakangas)
Тема pgsql: Revert patch to coerce 'unknown' type parameters in the backend.
Дата
Msg-id 20100819165449.D6F117541D7@cvs.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Log Message:
-----------
Revert patch to coerce 'unknown' type parameters in the backend. As Tom
pointed out, it would need a 2nd pass after the whole query is processed to
correctly check that an unknown Param is coerced to the same target type
everywhere. Adding the 2nd pass would add a lot more code, which doesn't
seem worth the risk given that there isn't much of a use case for passing
unknown Params in the first place. The code would work without that check,
but it might be confusing and the behavior would be different from the
varparams case.

Instead, just coerce all unknown params in a PL/pgSQL USING clause to text.
That's simple, and is usually what users expect.

Revert the patch in CVS HEAD and master, and backpatch the new solution to
8.4. Unlike the previous solution, this applies easily to 8.4 too.

Tags:
----
REL9_0_STABLE

Modified Files:
--------------
    pgsql/src/backend/parser:
        parse_param.c (r2.4.4.1 -> r2.4.4.2)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_param.c?r1=2.4.4.1&r2=2.4.4.2)
    pgsql/src/pl/plpgsql/src:
        pl_exec.c (r1.261.2.1 -> r1.261.2.2)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/pl_exec.c?r1=1.261.2.1&r2=1.261.2.2)

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

Предыдущее
От: heikki@postgresql.org (Heikki Linnakangas)
Дата:
Сообщение: pgsql: Revert patch to coerce 'unknown' type parameters in the backend.
Следующее
От: heikki@postgresql.org (Heikki Linnakangas)
Дата:
Сообщение: pgsql: Revert patch to coerce 'unknown' type parameters in the backend.