pg_stat_last_operation

The pg_stat_last_operation table contains metadata tracking information about database objects (tables, views, and so on).

Column Type References Description

Column	Type	References	Description
classid	oid	pg_class.oid	OID of the system catalog containing the object
objid	oid	any OID column	OID of the object within its system catalog
staactionname	name	—	The action that was taken on the object
stasysid	oid	pg_authid.oid	A foreign key to `pg_authid.oid`
stausename	name	—	The name of the role that performed the operation on this object
stasubtype	text	—	The type of object operated on or the subclass of operation performed
statime	timestamp with time zone	—	The timestamp of the operation. This is the same timestamp that is written to the Greengage DB server log files in case you need to look up more detailed information about the operation in the logs

classid

oid

pg_class.oid

OID of the system catalog containing the object

objid

oid

any OID column

OID of the object within its system catalog

staactionname

name

—

The action that was taken on the object

stasysid

oid

pg_authid.oid

A foreign key to pg_authid.oid

stausename

name

—

The name of the role that performed the operation on this object

stasubtype

text

—

The type of object operated on or the subclass of operation performed

statime

timestamp with time zone

—

The timestamp of the operation. This is the same timestamp that is written to the Greengage DB server log files in case you need to look up more detailed information about the operation in the logs

The pg_stat_last_operation table contains metadata tracking information about operations on database objects. This information includes the object ID, DDL action, user, type of object, and operation timestamp. Greengage DB updates this table when a database object is created, altered, truncated, vacuumed, analyzed, or partitioned, and when privileges are granted to an object.

If you want to track the operations performed on a specific object, use the objid value. Because the stasubtype value can identify either the type of object operated on or the subclass of operation performed, it is not a suitable parameter when querying the pg_stat_last_operation table.

The following example creates and replaces a view, and then shows how to use objid as a query parameter on the pg_stat_last_operation table:

CREATE VIEW trial AS SELECT * FROM gp_segment_configuration;
CREATE OR REPLACE VIEW trial AS SELECT * FROM gp_segment_configuration;
SELECT * FROM pg_stat_last_operation WHERE objid='trial'::regclass::oid;

The result:

 classid | objid | staactionname | stasysid | stausename | stasubtype |            statime
---------+-------+---------------+----------+------------+------------+-------------------------------
    1259 | 16430 | CREATE        |       10 | gpadmin    | VIEW       | 2025-12-02 14:54:07.882723+00
    1259 | 16430 | ALTER         |       10 | gpadmin    | SET        | 2025-12-02 14:54:11.382839+00
(2 rows)

Notice that the pg_stat_last_operation table entry for the view REPLACE operation specifies the ALTER action (staactionname) and the SET subtype (stasubtype).

pg_shdescription

pg_stat_last_shoperation