pgsql: Improve check for overly-long extensible node name.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Improve check for overly-long extensible node name.
Date: 2016-03-14 17:54:06
Message-ID: E1afWgw-0006Oq-U0@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Improve check for overly-long extensible node name.

The old code is bad for two reasons. First, it has an off-by-one
error. Second, it won't help if you aren't running with assertions
enabled. Per discussion, we want a check here in that case too.

Author: KaiGai Kohei, adjusted by me.
Reviewed-by: Petr Jelinek
Discussion: 56E0D547(dot)1030101(at)2ndquadrant(dot)com

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/3adf9ced17dfa84faa209127b4499e5a5b995806

Modified Files
--------------
src/backend/nodes/extensible.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-03-14 18:22:57 pgsql: Use repalloc_huge() to enlarge a SPITupleTable's tuple pointer a
Previous Message Robert Haas 2016-03-14 17:23:17 Re: Re: [COMMITTERS] pgsql: Only try to push down foreign joins if the user mapping OIDs mat