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

From Robert Haas
Subject pgsql: Improve check for overly-long extensible node name.
Date
Msg-id E1afWgw-0006Oq-U0@gemulon.postgresql.org
Whole thread Raw
List 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.1030101@2ndquadrant.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(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: pg_stat_get_progress_info() should be marked STRICT.
Next
From: Tom Lane
Date:
Subject: pgsql: Use repalloc_huge() to enlarge a SPITupleTable's tuple pointer a