Re: [HACKERS] Keep ECPG comment for log_min_duration_statement - Mailing list pgsql-hackers

From Okano, Naoki
Subject Re: [HACKERS] Keep ECPG comment for log_min_duration_statement
Date
Msg-id 0B4917A40C80E34BBEC4BE1A7A9AB7E27AB083@g01jpexmbkw05
Whole thread Raw
In response to Re: [HACKERS] Keep ECPG comment for log_min_duration_statement  (Michael Meskes <meskes@postgresql.org>)
Responses Re: [HACKERS] Keep ECPG comment for log_min_duration_statement
List pgsql-hackers
Thank you for your kind advise!

Michael Meskes wrote:
> The other option I can see, albeit without looking into details, is
> allowing all comments and then testing it for the right syntax after
> parsing. This could potentially also solve the above mentioned option
> problem.
This idea sounds great. But I am not sure that I can understand it correctly.

I understood the concept of this idea as following. Is it right?
1. The parser ignores comments/*...*/ as usual. That is, parser does not   identify comments as a token. 
2. After parsing, we parse again only to extract comments.
3. comments are put back or forth in SQL statement.

Regards,
Okano Naoki
Fujitsu

pgsql-hackers by date:

Previous
From: Artur Zakirov
Date:
Subject: Re: [HACKERS] Bug in to_timestamp().
Next
From: Etsuro Fujita
Date:
Subject: [HACKERS] postgres_fdw: support parameterized foreign joins