"Andrew And" <[EMAIL PROTECTED]> writes:
> Where have I find the description of the tables that Slony use?
>
>
>
> In my Data Base I have a lot tables that I show belo, but I don't have
> description about these.
>
>
>
> # SELECT * from _<CLUSTERNAME>.sl_ ;
> _<CLUSTERNAME>.sl_action_seq
> _<CLUSTERNAME>.sl_log_status _<CLUSTERNAME>.sl_sequence
> _<CLUSTERNAME>.sl_config_lock
> _<CLUSTERNAME>.sl_node _<CLUSTERNAME>.sl_set
> _<CLUSTERNAME>.sl_confirm
> _<CLUSTERNAME>.sl_nodelock _<CLUSTERNAME>.sl_setsync
> _<CLUSTERNAME>.sl_event
> _<CLUSTERNAME>.sl_nodelock_nl_conncnt_seq _<CLUSTERNAME>.sl_status
> _<CLUSTERNAME>.sl_event_seq
> _<CLUSTERNAME>.sl_path _<CLUSTERNAME>.sl_subscribe
> _<CLUSTERNAME>.sl_listen
> _<CLUSTERNAME>.sl_registry _<CLUSTERNAME>.sl_table
> _<CLUSTERNAME>.sl_local_node_id
> _<CLUSTERNAME>.sl_rowid_seq _<CLUSTERNAME>.sl_trigger
> _<CLUSTERNAME>.sl_log_1 _<CLUSTERNAME>.sl_seqlastvalue
> _<CLUSTERNAME>.sl_log_2 _<CLUSTERNAME>.sl_seqlog
You can find documentation in pg_catalog.pg_documentation.
You can list table descriptions by heading to the appropriate
namespace and issuing "\dt+", as follows:
oxrsorg=# set search_path to _cluster;
SET
oxrsorg=# \dt+
List of relations
Schema | Name | Type | Owner |
Description
----------+----------------+-------+-------+--------------------------------------------------------------------------------------------------------------------------------------------------------
_cluster | sl_config_lock | table | slony | This table exists solely to
prevent overlapping execution of configuration change procedures and the
resulting possible deadlocks.
_cluster | sl_confirm | table | slony | Holds confirmation of replication
events. After a period of time, Slony removes old confirmed events from both
this table and the sl_event table.
_cluster | sl_event | table | slony | Holds information about
replication events. After a period of time, Slony removes old confirmed events
from both this table and the sl_confirm table.
_cluster | sl_listen | table | slony | Indicates how nodes listen to
events from other nodes in the Slony-I network.
_cluster | sl_log_1 | table | slony | Stores each change to be
propagated to subscriber nodes
_cluster | sl_log_2 | table | slony | Stores each change to be
propagated to subscriber nodes
_cluster | sl_node | table | slony | Holds the list of nodes associated
with this namespace.
_cluster | sl_nodelock | table | slony | Used to prevent multiple slon
instances and to identify the backends to kill in terminateNodeConnections().
_cluster | sl_path | table | slony | Holds connection information for
the paths between nodes, and the synchronisation delay
_cluster | sl_seqlog | table | slony | Log of Sequence updates
_cluster | sl_sequence | table | slony | Similar to sl_table, each entry
identifies a sequence being replicated.
_cluster | sl_set | table | slony | Holds definitions of replication
sets.
_cluster | sl_setsync | table | slony | SYNC information
_cluster | sl_subscribe | table | slony | Holds a list of subscriptions on
sets
_cluster | sl_table | table | slony | Holds information about the tables
being replicated.
_cluster | sl_trigger | table | slony | Holds information about triggers
on tables managed using Slony-I
(16 rows)
You can also get information on individual tables, in the following fashion:
oxrsorg=# \d+ _cluster.sl_table
Table
"_cluster.sl_table"
Column | Type | Modifiers |
Description
-------------+---------+-----------+-----------------------------------------------------------------------------------------------------
tab_id | integer | not null | Unique key for Slony-I to use to identify
the table
tab_reloid | oid | not null | The OID of the table in
pg_catalog.pg_class.oid
tab_relname | name | not null | The name of the table in
pg_catalog.pg_class.relname used to recover from a dump/restore cycle
tab_nspname | name | not null | The name of the schema in
pg_catalog.pg_namespace.nspname used to recover from a dump/restore cycle
tab_set | integer | | ID of the replication set the table is in
tab_idxname | name | not null | The name of the primary index of the table
tab_altered | boolean | not null | Has the table been modified for
replication?
tab_comment | text | | Human-oriented description of the table
Indexes:
"sl_table-pkey" primary key, btree (tab_id)
"sl_table_tab_reloid_key" unique, btree (tab_reloid)
Foreign-key constraints:
"tab_set-set_id-ref" FOREIGN KEY (tab_set) REFERENCES sl_set(set_id)
--
(reverse (concatenate 'string "ofni.sailifa.ac" "@" "enworbbc"))
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
