DBLINK_ERROR_MESSAGE(3)

🎀 NAME 🎀

okay so welcome to DBLINK_ERROR_MESSAGE(3) — this is the little PostgreSQL page that tells you how to grab the last error message from a named connection. It’s giving “error receipts, but make it remote.” 💅

✨ SYNOPSIS ✨

dblink_error_message(text connname) returns text

🦋 DESCRIPTION 🦋

dblink_error_message fetches the most recent remote error message for a given connection. So if your remote connection has been going through it, this is where you go to read the drama. 😭

🌸 ARGUMENTS 🌸

• connname — the name of the connection to use. That’s the connection whose last error message you’re asking about, bestie. 💖

🫶 RETURN VALUE 🫶

It returns the last error message, or OK if there has been no error in this connection. So OK is literally the “no notes, we’re fine” response. ✨

💀 NOTES 💀

When asynchronous queries are initiated by dblink_send_query, the error message associated with the connection might not get updated until the server’s response message is consumed.

This typically means that dblink_is_busy or dblink_get_result should be called prior to dblink_error_message, so that any error generated by the asynchronous query will be visible. Translation: check the async situation first, or the error might still be backstage waiting for its main character moment. 👑🫠

🌈 EXAMPLES 🌈

SELECT dblink_error_message('dtest1');

made with 💖 from PostgreSQL 15.19 · 2026 · DBLINK_ERROR_MESSAGE(3)