Results of 1 - 2 of about 2 for recording (0.001 sec.)
- Profile and Monitor 11228
- Overview The JDBC driver exposes several ways to observe a running or completed query: cancelling and timing out queries, polling query progress, retrieving profiling output, and emitting memory-usage events through Java Flight Recorder . T
...t JFR support: nothing is emitted unless the application both sets the JDBC property on a connection and has an active JFR recording that enables the event. Enabling Emission Monitoring is opt-in per connection: set the jdbc_jfr_memory_monitor property to...ction conn = DriverManager.getConnection("jdbc:duckdb:/tmp/my_database", props)) { // work with the connection while a JFR recording is active } The same option can be set in the URL: jdbc:duckdb:/tmp/my_database;jdbc_jfr_memory_monitor=analytics-db Prope...ted, tagged with the given value. The JDBC property is only an enable and label switch. It does not control whether JFR is recording or the sampling period; those are governed by the JFR recording settings. Controlling the Period and Enabled State The sam... - https://man.mtool.work/duckdb/2.0/clients/java/profiling.html
- Security 7485
- This page covers Quack's security posture end to end: what the server exposes, what stays local, the role of a TLS-terminating reverse proxy, and the authentication / authorization callbacks the server runs on every connection and every que
...hentication hook that records sid → user pairs so authorization can look up who is asking. Because macros can't write, the recording side has to be a scalar UDF defined e.g. by a custom DuckDB extension. The authorization side can be a macro: -- (populate... - https://man.mtool.work/duckdb/2.0/quack/security.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work