Don't mix parameters for WKT with SQL. Either create the WKT (T for text) using conventional string utilities, then feed that string parameter to the query, or use an alternative geometry constructor that takes numeric parameters, such as ST_MakePoint(x, y)
.
The query should look something like this:
SELECT ST_AsText(the_geom) as location, name, intptlat, intptlon
FROM tiger_match
WHERE ST_DWithin(the_geom, ST_SetSRID(ST_MakePoint($intptlon, $intptlat), 4326), 0.1);
In general, don't buffer geometries to do proximity searches. In this case it was one point, but some folks also do this to whole tables, which is unnecessarily expensive. Also, your distance is 0.1 degree, which is a non-sense distance unit. If you use a geography
type, then it will use metric distances.