gp_log_database
The gp_toolkit.gp_log_database view uses an external table to read the server log files of the entire Greengage DB system (master, segments, and mirrors) and lists log entries associated with the current database.
Associated log entries can be identified by the session ID (logsession) and command ID (logcmdcount).
The use of this view requires superuser permissions.
| Column | Description |
|---|---|
logtime |
The timestamp of the log message |
loguser |
The name of the database user |
logdatabase |
The name of the database |
logpid |
The associated process ID (prefixed with |
logthread |
The associated thread (prefixed with |
loghost |
The segment or master host name |
logport |
The segment or master port |
logsessiontime |
Time session connection was opened |
logtransaction |
Global transaction ID |
logsession |
The session identifier (prefixed with |
logcmdcount |
The command number within a session (prefixed with |
logsegment |
The segment content identifier (prefixed with |
logslice |
The slice ID (portion of the query plan being run) |
logdistxact |
Distributed transaction ID |
loglocalxact |
Local transaction ID |
logsubxact |
Subtransaction ID |
logseverity |
The log severity level |
logstate |
SQL state code associated with the log message |
logmessage |
Log or error message text |
logdetail |
Detail message text associated with an error message |
loghint |
Hint message text associated with an error message |
logquery |
The internally generated query text |
logquerypos |
The cursor index into the internally generated query text |
logcontext |
The context in which this message gets generated |
logdebug |
Query string with full detail for debugging |
logcursorpos |
The cursor index into the query string |
logfunction |
The function in which this message is generated |
logfile |
The internal code file where the message originated |
logline |
The line of the code file where the message originated |
logstack |
Full text of the stack trace associated with this message |