Re: pg_stat_statements vs. SELECT FOR UPDATE - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: pg_stat_statements vs. SELECT FOR UPDATE
Date
Msg-id 875zuk6vb6.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: pg_stat_statements vs. SELECT FOR UPDATE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_stat_statements vs. SELECT FOR UPDATE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:

 > Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
 >> I propose that it should not ignore rowMarks, per the attached patch or
 >> something similar.

 Tom> +1 for not ignoring rowMarks, but this patch seems like a hack to
 Tom> me. Why didn't you just add RowMarkClause as one of the known
 Tom> alternative expression node types?

Because it's not an expression and nothing anywhere else in the backend
treats it as such?

-- 
Andrew (irc:RhodiumToad)


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Thread-unsafe coding in ecpg
Next
From: Michael Meskes
Date:
Subject: Re: Thread-unsafe coding in ecpg