scan.l: check_escape_warning() - Mailing list pgsql-hackers

From Michael Meskes
Subject scan.l: check_escape_warning()
Date
Msg-id 20080111151612.GA18802@feivel.credativ.de
Whole thread Raw
Responses Re: scan.l: check_escape_warning()  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: scan.l: check_escape_warning()  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Hi, 

could anyone please enlighten me whether this function is still needed?
AFAICT check_escape_warning() only has significant action if
warn_on_first_escape is true. This variable is set to true only on label
xqstart, but to false on xestart. However, check_escape_warning() and
check_string_escape_warning() btw. are only called in mode xe. Seems to
me that both are never called, or what am I missing?

Michael
-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!


pgsql-hackers by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Storage Model for Partitioning
Next
From: "Roberts, Jon"
Date:
Subject: could not open relation: Invalid argument