Logical Decoding Example
- The following example demonstartes the SQL interface.
+ The following example demonstrates the SQL interface.
Before you can use logical decoding, you must set
to logical and
- ot at least 1.
+ to at least 1.
Then, you should connect to the target database (in the example
below, postgres) as a superuser.
location | xid | data
-----------+-----+-----------------------------------------------
0/16E0478 | 689 | BEGIN 689
- 0/16E0478 | 689 | table public.data: INSERT: id[int4]:1 data[text]:'1'
- 0/16E0580 | 689 | table public.data: INSERT: id[int4]:2 data[text]:'2'
+ 0/16E0478 | 689 | table public.data: INSERT: id[integer]:1 data[text]:'1'
+ 0/16E0580 | 689 | table public.data: INSERT: id[integer]:2 data[text]:'2'
0/16E0650 | 689 | COMMIT 689
(4 rows)
location | xid | data
-----------+-----+-----------------------------------------------
0/16E09C0 | 690 | BEGIN 690
- 0/16E09C0 | 690 | table public.data: INSERT: id[int4]:3 data[text]:'3'
+ 0/16E09C0 | 690 | table public.data: INSERT: id[integer]:3 data[text]:'3'
0/16E0B90 | 690 | COMMIT 690
(3 rows)
location | xid | data
-----------+-----+-----------------------------------------------
0/16E09C0 | 690 | BEGIN 690
- 0/16E09C0 | 690 | table public.data: INSERT: id[int4]:3 data[text]:'3'
+ 0/16E09C0 | 690 | table public.data: INSERT: id[integer]:3 data[text]:'3'
0/16E0B90 | 690 | COMMIT 690
(3 rows)
location | xid | data
-----------+-----+-----------------------------------------------
0/16E09C0 | 690 | BEGIN 690
- 0/16E09C0 | 690 | table public.data: INSERT: id[int4]:3 data[text]:'3'
+ 0/16E09C0 | 690 | table public.data: INSERT: id[integer]:3 data[text]:'3'
0/16E0B90 | 690 | COMMIT 690 (at 2014-02-27 16:41:51.863092+01)
(3 rows)
# psql -c "INSERT INTO data(data) VALUES('4');"
# fg
BEGIN 693
-table public.data: INSERT: id[int4]:4 data[text]:'4'
+table public.data: INSERT: id[integer]:4 data[text]:'4'
COMMIT 693
CTRL-C
# pg_recvlogical -d testdb --slot test --drop
SNAPSHOT to read the state of the database at the moment
the slot was created. This transaction can then be used to dump the
database's state at that point in time which afterwards can be updated
- using the slot's contents without loosing any changes.
+ using the slot's contents without losing any changes.
backend's normal infrastructure, including calling output functions. Read
only access to relations is permitted as long as only relations are
accessed that either have been created by initdb in
- the pg_catalog schema, or have are marked as user
+ the pg_catalog schema, or have been marked as user
provided catalog tables using
ALTER TABLE user_catalog_table SET (user_catalog_table = true);
the begin and commit
callbacks. Transactions that were rolled back explicitly or implicitly
never get
- decoded. Successfull SAVEPOINTs are
+ decoded. Successful SAVEPOINTs are
folded into the transaction containing them in the order they were
- exectuded within that transaction.
+ executed within that transaction.
Startup Callback
The optional startup_cb callback is called whenever
- an replication slot is created or asked to stream changes, independent
+ a replication slot is created or asked to stream changes, independent
of the number of changes that are ready to be put out.
typedef void (*LogicalDecodeStartupCB) (
bool is_init
);
- The is_init paramter will be true when the
+ The is_init parameter will be true when the
replication slot is being created and false
otherwise.
options points to a struct of options
that output plugins can set: