If we want to save the SQL statement for some database objects(table, view,
etc.),
the backend will see the same problem. Here is an example.
create table s(sno int, sname char(10)); select 1;
I recall that some DBMS will store the statement for table s like this:
create table s(sno int,
Yep, I couldn't find a better way to do it when I added
debug_query_string long ago. Unless we go to a lot of work to parse the
string, we could end up with something worse than we have now.
---
Neil Conway wrote:
While
While reviewing Joachim Wieland's patch to add a pg_cursors system view,
I noticed that the patch assumes that debug_query_string contains the
portion of the submitted query string that corresponds to the SQL
statement we are currently executing. That is incorrect:
debug_query_string contains the
Neil Conway [EMAIL PROTECTED] writes:
While reviewing Joachim Wieland's patch to add a pg_cursors system view,
I noticed that the patch assumes that debug_query_string contains the
portion of the submitted query string that corresponds to the SQL
statement we are currently executing. That is
