Virtual Tables
[SHORE Storage Manager Application Programming Interface (SSM API)]

Collaboration diagram for Virtual Tables:

---

Detailed Description

Virtual tables are string representations of internal storage manager tables. These tables are experimental. If the tables get to be very large, they might fail.

• lock table (see ss_m::lock_collect) Columns are:
  • mode
  • duration
  • number of children
  • id of owning transaction
  • status (granted, waiting)
• transaction table (see ss_m::xct_collect) Columns are:
  • number of threads attached
  • global transaction id
  • transaction id
  • transaction state (in integer form)
  • coordinator
  • forced-readonly (Boolean)
• threads table (see ss_m::thread_collect) Columns are:
  • sthread ID
  • sthread status
  • number of I/Os issued
  • number of reads issued
  • number of writes issued
  • number of syncs issued
  • number of truncates issued
  • number of writev issued
  • number of readv issued
  • smthread name
  • smthread thread type (integer)
  • smthread pin count
  • is in storage manager
  • transaction ID of any attached transaction

Functions
static rc_t	ss_m::xct_collect (vtable_t &v, bool names_too=true)
	Collect transaction information in a virtual table.
static rc_t	ss_m::bp_collect (vtable_t &v, bool names_too=true)
	Collect buffer pool information in a virtual table.
static rc_t	ss_m::lock_collect (vtable_t &v, bool names_too=true)
	Collect lock table information in a virtual table.
static rc_t	ss_m::thread_collect (vtable_t &v, bool names_too=true)
	Collect thread information in a virtual table.

---

Function Documentation

static rc_t ss_m::xct_collect	(	vtable_t &	v,
		bool	names_too = true
	)			[static, inherited]

Collect transaction information in a virtual table.

Parameters:

[out]	v	The virtual table to populate.
[in]	names_too	If true, make the first row of the table a list of the attribute names.

All attribute values will be strings. The virtual table v can be printed with its output operator operator<< for ostreams.

Attention:

Not atomic. Can yield stale data.

Examples:

vtable_example.cpp.

static rc_t ss_m::bp_collect	(	vtable_t &	v,
		bool	names_too = true
	)			[static, inherited]

Collect buffer pool information in a virtual table.

Parameters:

[out]	v	The virtual table to populate.
[in]	names_too	If true, make the first row of the table a list of the attribute names.

Attention:

Be wary of using this with a large buffer pool.

All attribute values will be strings. The virtual table v can be printed with its output operator operator<< for ostreams.

Attention:

Not atomic. Can yield stale data.

static rc_t ss_m::lock_collect	(	vtable_t &	v,
		bool	names_too = true
	)			[static, inherited]

Collect lock table information in a virtual table.

Parameters:

[out]	v	The virtual table to populate.
[in]	names_too	If true, make the first row of the table a list of the attribute names.

All attribute values will be strings. The virtual table v can be printed with its output operator operator<< for ostreams.

Attention:

Not atomic. Can yield stale data. Cannot be used in a multi-threaded-transaction context.

Examples:

vtable_example.cpp.

static rc_t ss_m::thread_collect	(	vtable_t &	v,
		bool	names_too = true
	)			[static, inherited]

Collect thread information in a virtual table.

Parameters:

[out]	v	The virtual table to populate.
[in]	names_too	If true, make the first row of the table a list of the attribute names.

All attribute values will be strings. The virtual table v can be printed with its output operator operator<< for ostreams.

Attention:

Not thread-safe. Can yield stale data.

Examples:

vtable_example.cpp.

---