Server output when run SQL query

[supavit28]

I am migrate to use dbx from dbeaver/datagrip. Its lightweight is superb.

Now I found that dbx will show output on Messages tab only when query is finished (not canceled or get error), while dbeaver dbeaver/datagrip can catch server output log when run SQL query real time.

Is there any chance that dbx will support this feature, or it already have if using jdbc driver ? Please advice

SQL example on Postgres database

SET client_min_messages = NOTICE;
DO $$ 
BEGIN
    FOR i IN 1..10 LOOP
        RAISE NOTICE 'Real-time message at %', clock_timestamp();
        PERFORM pg_sleep(2);
    END LOOP;
END $$;

If run on dbeaver/datagrip, output

Real-time message at ....

will print every 2 seconds but dbx will show when finished only (if cancel before finish log will also not show)

[jamalkamaladdin]

Not today, and JDBC does not change it. Postgres driver attaches buffered RAISE NOTICE messages after your statement finishes, and JDBC agent reads getWarnings() after execution too. Live output needs new code, so open an issue asking for it.

dbx/crates/dbx-driver-postgres/src/postgres.rs

Lines 8695 to 8738 in b281fbd

	let client = checkout_postgres_client(pool, None, super::connection_timeout()).await?;
	let client = &EncodingClient::new(&client);
	// Drop stale notices from infrastructure statements so only messages raised
	// by this statement are attached to its result.
	let _ = drain_postgres_notices(client).await;
	let result = if postgres_statement_returns_rows(sql) {
	execute_select_query(client, sql, start, row_limit).await
	} else {
	client.execute(sql, &[]).await.map_err(pg_error_to_string).map(|affected| {
	clear_postgres_caches_after_ddl(pool, Some(client), sql);
	QueryResult {
	columns: vec![],
	column_types: Vec::new(),
	column_sortables: Vec::new(),
	spatial_columns: vec![],
	spatial_values: vec![],
	rows: vec![],
	affected_rows: affected,
	execution_time_ms: start.elapsed().as_millis(),
	server_execute_time_us: None,
	query_timings_ms: None,
	truncated: false,
	session_id: None,
	has_more: false,
	elasticsearch_raw_body: None,
	messages: Vec::new(),
	}
	})
	};
	match result {
	Ok(mut result) => {
	result.messages = drain_postgres_notices(client).await;
	Ok(result)
	}
	Err(error) => {
	// Drop notices so an errored statement's messages cannot leak into
	// the next query on this pooled connection.
	let _ = drain_postgres_notices(client).await;
	Err(error)
	}
	}

[t8y2]

Implemented in 12b16cb02, planned for v0.6.40.

With the desktop app's native PostgreSQL driver, your RAISE NOTICE / pg_sleep example now appends output to Messages while the SQL is still running. Messages already received remain visible if you cancel execution or the SQL raises an error. The implementation also covers the manual-transaction execution path, resets output for each execution, and bounds the retained output.

This is currently desktop native PostgreSQL only. Switching to JDBC does not enable live output: JDBC and the Web HTTP transport still display messages after execution returns. The Kingbase Agent message-capture fix in the same commit is also completion-time output, not live streaming.

Verified against PostgreSQL 18.6 on our test server, including output before completion, successful execution, SQL errors, cancellation, and isolation from the next query; focused regression tests and affected-package checks also pass.

Please upgrade to v0.6.40 once it is released and retry using a native PostgreSQL connection. Keep client_min_messages = NOTICE as in your example. If the problem persists, please open an issue with the DBX/PostgreSQL versions, connection driver, reproduction SQL and logs, and link this discussion. Related feature request: #2725.