Re: Slony

Parece que esta tabla si que la usa

CREATE TABLE _slony_questionity.sl_event
(
ev_origin integer NOT NULL, -- The ID # (from sl_node.no_id) of the
source node for this event
ev_seqno bigint NOT NULL, -- The ID # for the event
ev_timestamp timestamp without time zone, -- When this event record was
created
ev_minxid _slony_questionity.xxid, -- Earliest XID on provider node for
this event
ev_maxxid _slony_questionity.xxid, -- Latest XID on provider node for
this event
ev_xip text, -- List of XIDs, in order, that are part of this event
ev_type text, -- The type of event this record is for. ...
ev_data1 text, -- Data field containing an argument needed to process the
event
ev_data2 text, -- Data field containing an argument needed to process the
event
ev_data3 text, -- Data field containing an argument needed to process the
event
ev_data4 text, -- Data field containing an argument needed to process the
event
ev_data5 text, -- Data field containing an argument needed to process the
event
ev_data6 text, -- Data field containing an argument needed to process the
event
ev_data7 text, -- Data field containing an argument needed to process the
event
ev_data8 text, -- Data field containing an argument needed to process the
event
CONSTRAINT "sl_event-pkey" PRIMARY KEY (ev_origin, ev_seqno)
)
WITH (
OIDS=FALSE
);
ALTER TABLE _slony_questionity.sl_event OWNER TO postgres;
COMMENT ON TABLE _slony_questionity.sl_event IS 'Holds information about
replication events. After a period of time, Slony removes old confirmed
events from both this table and the sl_confirm table.';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_origin IS 'The ID # (from
sl_node.no_id) of the source node for this event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_seqno IS 'The ID # for the
event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_timestamp IS 'When this
event record was created';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_minxid IS 'Earliest XID on
provider node for this event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_maxxid IS 'Latest XID on
provider node for this event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_xip IS 'List of XIDs, in
order, that are part of this event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_type IS 'The type of event
this record is for.
SYNC = Synchronise
STORE_NODE =
ENABLE_NODE =
DROP_NODE =
STORE_PATH =
DROP_PATH =
STORE_LISTEN =
DROP_LISTEN =
STORE_SET =
DROP_SET =
MERGE_SET =
SET_ADD_TABLE =
SET_ADD_SEQUENCE =
STORE_TRIGGER =
DROP_TRIGGER =
MOVE_SET =
ACCEPT_SET =
SET_DROP_TABLE =
SET_DROP_SEQUENCE =
SET_MOVE_TABLE =
SET_MOVE_SEQUENCE =
FAILOVER_SET =
SUBSCRIBE_SET =
ENABLE_SUBSCRIPTION =
UNSUBSCRIBE_SET =
DDL_SCRIPT =
ADJUST_SEQ =
RESET_CONFIG =
';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_data1 IS 'Data field
containing an argument needed to process the event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_data2 IS 'Data field
containing an argument needed to process the event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_data3 IS 'Data field
containing an argument needed to process the event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_data4 IS 'Data field
containing an argument needed to process the event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_data5 IS 'Data field
containing an argument needed to process the event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_data6 IS 'Data field
containing an argument needed to process the event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_data7 IS 'Data field
containing an argument needed to process the event';
COMMENT ON COLUMN _slony_questionity.sl_event.ev_data8 IS 'Data field
containing an argument needed to process the event';

El 22 de noviembre de 2011 23:09, felipe fernandez
<ffdezrguez(at)gmail(dot)com>escribió:

> pg_dump: restableciendo datos de la tabla «sl_archive_counter»
> pg_dump: extrayendo el contenido de la tabla sl_archive_counter
> pg_dump: restableciendo datos de la tabla «sl_config_lock»
> pg_dump: extrayendo el contenido de la tabla sl_config_lock
> pg_dump: restableciendo datos de la tabla «sl_confirm»
> pg_dump: extrayendo el contenido de la tabla sl_confirm
> pg_dump: restableciendo datos de la tabla «sl_event»
> pg_dump: extrayendo el contenido de la tabla sl_event
> pg_dump: la orden SQL falló
> pg_dump: Mensaje de error del servidor: ERROR: could not access file
> "$libdir/xxid": No such file or directory
> pg_dump: La orden era: COPY _slony_questionity.sl_event (ev_origin,
> ev_seqno, ev_timestamp, ev_minxid, ev_maxxid, ev_xip, ev_type, ev_data1,
> ev_data2, ev_data3, ev_data4, ev_data5, ev_data6, ev_data7, ev_data8) TO
> stdout;
> pg_dump: *** se abortó a causa de un error
>
> El 22 de noviembre de 2011 23:01, Jaime Casanova <jaime(at)2ndquadrant(dot)com>escribió:
>
> On Tue, Nov 22, 2011 at 4:57 PM, felipe fernandez <ffdezrguez(at)gmail(dot)com>
>> wrote:
>> > Estimados, seguramente para vosotros esto es coser y cantar
>>
>> espero que no porque coso y canto muy mal... ;)
>>
>> --
>> Jaime Casanova www.2ndQuadrant.com
>> Professional PostgreSQL: Soporte 24x7 y capacitación
>>
>
>
>
> --
> Salu2
>
> Felipe Fernández Rguez
> "Uno se alegra de resultar útil" Andrew Martin "El hombre bicentenario"
> Isaac Asimov.
> "Documentation is like sex: when it is good, it is very, very good; and
> when it is bad, it is better than nothing."
>
>

--
Salu2

Felipe Fernández Rguez
"Uno se alegra de resultar útil" Andrew Martin "El hombre bicentenario"
Isaac Asimov.
"Documentation is like sex: when it is good, it is very, very good; and
when it is bad, it is better than nothing."