New line characters removed from request column in v_monitor.query_requests

node_name           | v_dev_node0001
user_name           | daniel
session_id          | synapse-2677:0x1f0
request_id          | 6
transaction_id      | 45035996273725090
statement_id        | 6
request_type        | QUERY
request             | SELECT 1  FROM transactions;
request_label       | 
search_path         | "$user", public, v_catalog, v_monitor, v_internal
memory_acquired_mb  | 
success             | t
error_count         | 
start_timestamp     | 2015-01-07 11:44:18.832581+02
end_timestamp       | 2015-01-07 11:44:19.133265+02
request_duration_ms | 301
is_executing        | f

SELECT /*+label(comment)*/ 1 -- revenue
FROM transactions;

daniel=>  select * from query_requests where request_label = 'comment';
-[ RECORD 1 ]-------+--------------------------------------------------
node_name           | v_dev_node0001
user_name           | daniel
session_id          | synapse-2677:0x1f0
request_id          | 9
transaction_id      | 45035996273725090
statement_id        | 9
request_type        | QUERY
request             | SELECT /*+label(comment)*/ 1  FROM transactions;
request_label       | comment
search_path         | "$user", public, v_catalog, v_monitor, v_internal
memory_acquired_mb  | 
success             | t
error_count         | 
start_timestamp     | 2015-01-07 11:47:19.820904+02
end_timestamp       | 2015-01-07 11:47:20.127018+02
request_duration_ms | 307
is_executing        | f

daniel=> select version();
-[ RECORD 1 ]-------------------------------
version | Vertica Analytic Database v7.1.1-2

We don't control what clients analysts use to connect to Vertica.

Additionally the comments can be helpful in understanding queries in the log so we'd prefer not to truncate them.

I've discovered that the table v_internal.dc_requests_issued also has a request column

• http://my.vertica.com/docs/7.1.x/HTML/index.htm#Authoring/SQLReferenceManual/Functions/VerticaFuncti...
• http://my.vertica.com/docs/7.1.x/HTML/index.htm#Attic/Troubleshooting/QueryingDataCollectorTables.ht...
• http://my.vertica.com/docs/7.1.x/HTML/index.htm#Attic/Troubleshooting/WorkingWithDataCollectionLogs....

daniel=> select table_name from v_monitor.DATA_COLLECTOR where table_name ilike '%request%';
      table_name       
-----------------------
 dc_lock_requests
 dc_requests_completed
 dc_requests_issued
 dc_requests_retried
(4 rows)

daniel=> select data_collector_help();
data_collector_help

Usage Data Collector
The data collector retains history of important system activities.
  This data can be used as a reference of what actions have been taken by users,
    but it can also be used to locate performance bottlenecks, or identify
    potential improvements to the Vertica configuration.
  This data is queryable via Vertica system tables.

The list of data collector components, and some statistics, can be found using:
  SELECT * FROM v_monitor.data_collector;

The amount of data retained by size and time can be controlled with several functions.
  To just set the size amount:
    set_data_collector_policy(<component>,
                            <memory retention (KB)>,
                            <disk retention (KB)>);

  To set both the size and time amounts (the smaller one will dominate):
    set_data_collector_policy(<component>,
                            <memory retention (KB)>,
                            <disk retention (KB)>,
                            <interval>);

  To set just the time amount:
    set_data_collector_time_policy(<component>,
                            <interval>);
  To set just the time amount for all tables:
    set_data_collector_time_policy(<interval>);

The current retention policy for a component can be queried with:
  get_data_collector_policy(<component>);

Data on disk is kept in the "DataCollector" directory under the Vertica
  catalog path.  This directory also contains instructions on how to load
  the monitoring data into another Vertica database.

To move the data collector logs and instructions to other storage locations,
  create labeled storage locations using add_location and then use:
  set_data_collector_storage_location(<storage_label>);

Additional commands can be used to affect the data collection logs.
  The log can be cleared with:
     clear_data_collector([<optional component>]);
  The log can be synchronized with the disk storage using:
     flush_data_collector([<optional component>]);


(1 row)
daniel=> 

FYI: v_internal.dc_requests_issued isn't broken, like v_monitor.query_requests.

@jbondurant_gsn, this isn't really broken. It is as intended. v_monitor.query_requests is basically a view into v_internal.dc_requests_issued. If you look at the view definition, it intentionally removes all line breaks. If line breaks are required - then, as you suggested, use dc_requests_issued that has the raw data.