SVL_S3QUERY
Use the SVL_S3QUERY view to get details about Amazon Redshift Spectrum queries at the segment and node slice level.
SVL_S3QUERY is visible to all users. Superusers can see all rows; regular users can see only their own data. For more information, see Visibility of data in system tables and views.
Note
SVL_S3QUERY only contains queries run on main clusters. It doesn't contain queries run on concurrency scaling clusters. To access queries run on both main and concurrency scaling clusters, we recommend that you use the SYS monitoring view SYS_EXTERNAL_QUERY_DETAIL . The data in the SYS monitoring view is formatted to be easier to use and understand.
Table columns
| Column name | Data type | Description |
|---|---|---|
| userid | integer | The ID of user who generated a given entry. |
| query | integer | The query ID. |
| segment | integer | A segment number. A query consists of multiple segments, and each segment consists of one or more steps. |
| step | integer | The query step that ran. |
| node | integer | The node number. |
| slice | integer | The data slice that a particular segment ran against. |
| starttime | timestamp | Time in UTC that the query started executing. |
| endtime | timestamp | Time in UTC that the query execution completed |
| elapsed | integer | Elapsed time (in microseconds). |
| external_table_name | char(136) | Internal format of external table name for the s3 scan step. |
| is_partitioned | char(1) | If true (t), this column
value indicates that the external table is partitioned. |
| is_rrscan | char(1) | If true (t), this column
value indicates that a range-restricted scan was applied. |
| s3_scanned_rows | bigint | The number of rows scanned from Amazon S3 and sent to the Redshift Spectrum layer. |
| s3_scanned_bytes | bigint | The number of bytes scanned from Amazon S3 and sent to the Redshift Spectrum layer. |
| s3query_returned_rows | bigint | The number of rows returned from the Redshift Spectrum layer to the cluster. |
| s3query_returned_bytes | bigint | The number of bytes returned from the Redshift Spectrum layer to the cluster. |
| files | integer | The number of files that were processed for this S3 scan step on this slice. |
| splits | int | The number of splits processed on this slice. With large splitable data files, for example, data files larger than about 512 MB, Redshift Spectrum tries to split the files into multiple S3 requests for parallel processing. |
| total_split_size | bigint | The total size of all splits processed on this slice, in bytes. |
| max_split_size | bigint | The maximum split size processed for this slice, in bytes. |
| total_retries | integer | The total number of retries for the processed files. |
| max_retries | integer | The maximum number of retries for an individual processed file. |
| max_request_duration | integer | The maximum duration of an individual Redshift Spectrum request (in microseconds). |
| avg_request_duration | double precision | The average duration of the Redshift Spectrum requests (in microseconds). |
| max_request_parallelism | integer | The maximum number of outstanding Redshift Spectrum on this slice for this S3 scan step. |
| avg_request_parallelism | double precision | The average number of parallel Redshift Spectrum requests on this slice for this S3 scan step. |
Sample query
The following example gets the scan step details for the last query completed.
select query, segment, slice, elapsed, s3_scanned_rows, s3_scanned_bytes, s3query_returned_rows, s3query_returned_bytes, files from svl_s3query where query = pg_last_query_id() order by query,segment,slice;
query | segment | slice | elapsed | s3_scanned_rows | s3_scanned_bytes | s3query_returned_rows | s3query_returned_bytes | files ------+---------+-------+---------+-----------------+------------------+-----------------------+------------------------+------ 4587 | 2 | 0 | 67811 | 0 | 0 | 0 | 0 | 0 4587 | 2 | 1 | 591568 | 172462 | 11260097 | 8513 | 170260 | 1 4587 | 2 | 2 | 216849 | 0 | 0 | 0 | 0 | 0 4587 | 2 | 3 | 216671 | 0 | 0 | 0 | 0 | 0