[COMMITTERS] pgsql: Avoid coercing a whole-row variable that is already coerced.

Поиск
Список
Период
Сортировка
От Robert Haas
Тема [COMMITTERS] pgsql: Avoid coercing a whole-row variable that is already coerced.
Дата
Msg-id E1e2kqF-0001aB-8g@gemulon.postgresql.org
обсуждение исходный текст
Ответы Re: [COMMITTERS] pgsql: Avoid coercing a whole-row variable that is already coerced.
Список pgsql-committers
Avoid coercing a whole-row variable that is already coerced.

Marginal efficiency and beautification hack.  I'm not sure whether
this case ever arises currently, but the pending patch for update
tuple routing will cause it to arise.

Amit Khandekar

Discussion: http://postgr.es/m/CAJ3gD9cazfppe7-wwUbabPcQ4_0SubkiPFD1+0r5_DkVNWo5yg@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1c497fa72df7593d8976653538da3d0ab033207f

Modified Files
--------------
src/backend/rewrite/rewriteManip.c | 53 ++++++++++++++++++++++++++++++--------
1 file changed, 42 insertions(+), 11 deletions(-)


--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

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

Предыдущее
От: Robert Haas
Дата:
Сообщение: [COMMITTERS] pgsql: Use ResultRelInfo ** rather than ResultRelInfo * for tuplerouti
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Avoid coercing a whole-row variable that is already coerced.