GS_RECYCLEBIN
GS_RECYCLEBIN describes details about objects in the recycle bin of the flashback feature.
Name | Type | Description |
|---|---|---|
oid | oid | System column |
rcybaseid | oid | Base table object ID, which references gs_recyclebin.oid |
rcydbid | oid | OID of the database to which the current object belongs |
rcyrelid | oid | OID of the current object |
rcyname | name | Name of the object in the recycle bin. The format is BIN$unique_id$oid$0. unique_id indicates the unique identifier with a maximum of 16 characters, and oid indicates the OID. |
rcyoriginname | name | Original object name |
rcyoperation | char | Operation type. The options are as follows:
|
rcytype | integer | Object type. The options are as follows:
|
rcyrecyclecsn | bigint | CSN when an object is dropped or truncated |
rcyrecycletime | timestamp with time zone | Time when an object is dropped or truncated |
rcycreatecsn | bigint | CSN when an object is created |
rcychangecsn | bigint | SCN when an object definition is modified |
rcynamespace | oid | OID of the namespace that contains this relationship |
rcyowner | oid | Owner of the relationship |
rcytablespace | oid | Tablespace in which this relationship is stored. If the value is 0, the default tablespace of the database is used. This column is meaningless if the relationship has no on-disk file. |
rcyrelfilenode | oid | File name of the recycle bin object on a disk, or 0 if none, which is used to restore the physical file when the TRUNCATE object is restored. |
rcycanrestore | Boolean | Specifies whether flashback can be performed separately. |
rcycanpurge | Boolean | Specifies whether the purge operation can be performed independently. |
rcyfrozenxid | xid32 | All transaction IDs before this one have been replaced with a permanent ("frozen") transaction ID in the table. |
rcyfrozenxid64 | xid | All transaction IDs before this one have been replaced with a permanent ("frozen") transaction ID in the table. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.

