Skip to content

Messages, and where they are explained

The messages the app shows when a pipeline stops or a connection test fails, each linked to the page that explains it. Search finds any of them by its words.

A stopped pipeline’s history names why, in one of these titles; each is explained on the pages under it.

Stopped: a schema change waits for your decision

Section titled “Stopped: a schema change waits for your decision”

Stopped: a table was truncated at the source

Section titled “Stopped: a table was truncated at the source”

Stopped: the source left out a value a row needs

Section titled “Stopped: the source left out a value a row needs”

Stopped: your destination did not keep some rows

Section titled “Stopped: your destination did not keep some rows”

Stopped: your destination refused our access

Section titled “Stopped: your destination refused our access”

Stopped: a name your destination cannot take

Section titled “Stopped: a name your destination cannot take”

Stopped: rows already in your destination stop the write

Section titled “Stopped: rows already in your destination stop the write”

Stopped: a source table has no key your destination can use

Section titled “Stopped: a source table has no key your destination can use”

Stopped: a table’s filter or column setting cannot be applied

Section titled “Stopped: a table’s filter or column setting cannot be applied”

Stopped: the source’s publication changed

Section titled “Stopped: the source’s publication changed”

Stopped: a change to a table with no key could not be placed

Section titled “Stopped: a change to a table with no key could not be placed”

Stopped: your source database’s history changed

Section titled “Stopped: your source database’s history changed”

Stopped: your source database’s identity changed

Section titled “Stopped: your source database’s identity changed”

Stopped: history was removed before this export read it

Section titled “Stopped: history was removed before this export read it”
The test says Code Read
A column’s type has no destination type. unmappable the reference
A failover upstream of this replica, or its own promotion, continues when everything we can check continues. One that lost transactions we had read and then caught up can go unnoticed: grant this user REPLICATION to have it judged exactly. plain_replica the reference
A foreign key joins two of the tables. foreign_key_between_tables the reference
A function named as one of Aurora’s own exists outside pg_catalog, so the test could not confirm this is not an Aurora reader. aurora_unconfirmed the reference
A generated column is not sent by the publication. generated_unsent_under_full the reference
A lock held by another session blocked this read. lock_wait the reference
A name you picked is not a table, a view for example. A query-based pipeline syncs a view only with the key columns you name for it (key_columns, through the API); this list picks tables. not_a_table the reference
A pg_hba.conf line rejects this connection. hba_reject_line what to do; the reference
A read took longer than 5 seconds. read_timed_out the reference
A replica cannot read an unlogged table: read it from the primary. unlogged_on_standby the reference
A restore to a point in time starts a new timeline, which stops this pipeline as a failover does. A disk or VM snapshot, or a backup brought back as it was, keeps the timeline. It is detected for certain while your database is behind what we last read. Once it has caught up, it goes unnoticed, and then rows your database wrote soon after it can be missing from your destination or keep older values, for good on a table that is only inserted into. We tell you when your database restarts. After any restore you know of, re-sync. restore the reference
A server behind this address does not report how far it has replayed: use one replica’s own address. replica_position_unreadable the reference
A switchover or a failover that lost nothing continues, and we tell you; one that lost what we read stops before reading and asks you to re-sync. exact the reference
A table has no column the destination can write. no_writable_columns the reference
A table has no primary key. no_key the reference
A table is not in the publication. not_published the reference
A table is not on this server. table_missing the reference
A virtual generated column under REPLICA IDENTITY FULL makes the source refuse the table’s UPDATE and DELETE. virtual_under_full the reference
AWS’s record of the Aurora cluster does not name this instance its writer: connect to the cluster’s writer. aurora_writer_unconfirmed the reference
AWS’s record of the Aurora cluster’s writer could not be read, so this instance was judged by recovery alone. aurora_writer_unverified the reference
After a failover or a planned switchover (such as your provider’s maintenance) we ask you whether to continue, showing what we could check; this user cannot read where the new history began. Grant it REPLICATION to have this judged exactly. plain_primary the reference
An idle change bookmark (replication slot) is dropped in under a day. idle_slot_timeout_short the reference
Another session is reading the change bookmark (replication slot). slot_in_use the reference
Channel binding is required, and the server did not use it. channel_binding_unavailable the reference
Channel binding was removed on the way: something between us and the server rewrites the sign-in. channel_binding_stripped the reference
Checked for each table once you pick them. no_tables_picked the reference
Connected under a mode that does not verify the server. weak_mode the reference
Every WAL sender is in use. no_free_sender what to do; the reference
Every change bookmark (replication slot) the server allows is in use. no_free_slot what to do; the reference
No host key is approved for this bastion yet. Compare the one it presents with the bastion’s own, then approve it. host_key_approval_needed the reference
Not used: a pipeline that reads its tables by queries needs no published tables (publication), change bookmark (replication slot) or logical replication settings. query_based the reference
Not yet verified on this provider: a crash just before a sync is a case we have not proven safe there. provider_untested the reference
Nothing answered within 10 seconds: a firewall dropping the connection is the usual cause. timed_out what to do; the reference
PostgreSQL 13 is past its end of life: upgrade when you can. version_past_end_of_life the reference
PostgreSQL 13 reads each table in one statement, holding its lock for the whole read. lock_hint the reference
Reading tables by queries needs PostgreSQL 13 or later. query_version_too_old the reference
Row-level security would hide rows from this pipeline. row_secured the reference
Signed in by MD5, which PostgreSQL 18 deprecates. auth_md5_deprecated the reference
Some tables are large, and every sync reads each one whole. scan_large the reference
The SSH bastion could not be reached, or the session to it ended. ssh_unreachable the reference
The SSH session to the bastion could not be set up: the port may not be SSH, the bastion offers no algorithm this service uses, or it sent a host key or key-exchange message that could not be read or did not verify. ssh_handshake_failed the reference
The SSH tunnel failed for a reason on our side. ssh_failed the reference
The TLS handshake failed. handshake_failed the reference
The agent enrolled a key that nobody has approved yet. Compare its fingerprint with the line the agent printed, then approve it in Settings, Network and security, Proxy agents. agent_awaiting_approval the reference
The agent is connected but did not open a connection within 10 s. agent_unresponsive the reference
The agent is not connected. Its pipelines resume on their own when it connects. agent_offline the reference
The agent was deleted. Point this source at another agent. agent_deleted the reference
The bastion could not connect to the database. ssh_target_unreachable the reference
The bastion offers only a host key this service does not verify (RSA or DSA). host_key_algorithm_unsupported the reference
The bastion presents a different host key from the one approved. host_key_changed the reference
The bastion refused our key: the line below is not in the SSH user’s authorized_keys. ssh_auth_refused the reference
The bastion refused to forward to the database: AllowTcpForwarding or the line’s permitopen does not allow it. ssh_forwarding_refused the reference
The certificate is valid, but issued for another name. name_mismatch what to do; the reference
The change bookmark (replication slot) belongs to another database. slot_wrong_database the reference
The change bookmark (replication slot) does not exist yet. slot_missing the reference
The change bookmark (replication slot) is a standby’s synced copy, which cannot be read. slot_is_synced_copy the reference
The change bookmark (replication slot) is kept through a failover, but no standby is listed for it to wait for. failover_without_standby_slots the reference
The change bookmark (replication slot) is not a logical one. slot_not_logical the reference
The change bookmark (replication slot) no longer reserves its log. slot_unreserved the reference
The change bookmark (replication slot) uses another output plugin. slot_wrong_plugin the reference
The change bookmark (replication slot) was invalidated. slot_invalidated the reference
The client certificate is not this role’s. client_certificate_role_mismatch the reference
The connection to the agent was refused for a reason on our side. It is retried. agent_ticket_refused the reference
The connection was lost part way. connection_lost the reference
The connection was refused or reset. unreachable what to do; the reference
The connection’s settings could not be used. configuration the reference
The database does not exist. database_missing what to do; the reference
The destination cannot be used as configured. destination_unusable the reference
The destination could not resolve the role. role_unresolved the reference
The destination database is not UTF8, or its connection does not speak UTF8, and a PostgreSQL destination must be a UTF8 database. encoding_not_utf8 the reference
The destination is the source: the pipeline would read its own writes. write_loop the reference
The destination refused a permission the pipeline needs. permission_denied the reference
The destination refused the key. key_refused the reference
The destination refuses the table. destination_blocked the reference
The host has only IPv4 addresses, and this service connects from IPv6. ipv4_only the reference
The host has only IPv6 addresses, and this service connects from IPv4. ipv6_only what to do; the reference
The host name was not found within 5 seconds. timed_out what to do; the reference
The password crossed a connection whose server is not verified. auth_cleartext_unverified the reference
The password was refused. The server says the same for a role that does not exist, or whose password has expired. bad_password what to do; the reference
The permission test gave no answer, so whether the role may create what a pipeline needs is not known. Test again. permission_unanswered the reference
The pgoutput plugin is not allowed on this server. pgoutput_not_allowed the reference
The publication covers less than the pipeline asks for. publication_narrowed the reference
The publication withholds a key column. key_withheld the reference
The publication’s column list does not fit the table’s REPLICA IDENTITY FULL. column_list_under_full the reference
The published tables (publication) do not exist yet. publication_missing the reference
The role cannot replicate: it needs the REPLICATION attribute. not_replication_role what to do; the reference
The role does not exist. role_missing the reference
The role is not granted to this user. role_not_granted the reference
The role may not connect to this database. no_connect_privilege what to do; the reference
The role may not log in (NOLOGIN). role_cannot_log_in what to do; the reference
The server answered with an error. server_error the reference
The server asked for a password and none was given. no_password the reference
The server asked for a sign-in method this service does not use. auth_unsupported the reference
The server does not offer TLS. server_has_no_tls what to do; the reference
The server has no free connection. too_many_connections what to do; the reference
The server presents a different certificate from the one approved. certificate_changed what to do; the reference
The server refused a privilege this sign-in needs: CONNECT on the database, or REPLICATION. privilege_refused the reference
The server refused the role: it does not exist, or may not log in. role_refused the reference
The server requires a client certificate. client_certificate_required the reference
The server’s certificate has expired. expired the reference
The server’s certificate is not signed by anything this connection trusts. approval_needed what to do; the reference
The server’s certificate was refused. certificate_rejected the reference
The server’s encoding is not UTF-8. encoding_not_utf8 the reference
The server’s identity could not be read. identity_unavailable the reference
The server’s pg_hba.conf has no line for this connection. no_hba_line what to do; the reference
The server’s pg_hba.conf refused this connection. hba_refused the reference
The server’s sign-in method refused this role. auth_method_refused the reference
The server, or something answering in its place, signed in without proving it holds the password, so the connection was dropped: something between us and the server may be standing in for it. server_unproven the reference
The session did not take the search path the pipeline sets; a pooler or proxy may have dropped it. search_path_unpinned the reference
The sign-in could not be bound to this TLS session: something between us and the server ends the TLS. channel_binding_mismatch the reference
The sign-in was refused for a reason the server’s answer does not let us place. sign_in_refused the reference
There is no certificate to verify the server against. no_trust_anchors the reference
This PostgreSQL major is not one our tests run against. version_untested the reference
This PostgreSQL version is too old for logical replication here. version_too_old the reference
This address reaches more than one server: every read waits for one that is not behind what we last read. several the reference
This could not be read. unreadable the reference
This is an Aurora reader instance: connect to the cluster’s writer. aurora_reader the reference
This is an Aurora reader, or this user cannot show it is the writer: connect to your cluster’s writer endpoint. aurora_reader_untested the reference
This replica may cancel our reads to replay changes from the primary. standby_cancels_reads the reference
This server’s timeline cannot be read, so a failover would not be detected. source_history_unknown the reference
This standby cancels long reads within 15 minutes. standby_delay_short the reference
This standby has hot_standby_feedback off. hot_standby_feedback_off the reference
This step did not finish within its time limit. timed_out the reference
This user cannot read how far the server’s log is on disk, which every sync checks. durability_unreadable the reference
This user may not lock a table to read it: grant SELECT on the table itself. lock_refused the reference
This user may not read a table’s rows with their xmin: grant SELECT on the table. xmin_refused the reference
Your database does not keep the change log a pipeline reads: its wal_level setting is not logical. wal_level_not_logical what to do; the reference
fsync is off on this server, so a crash can lose changes it reported as written. fsync_off the reference
synchronous_commit is off on this server, so a crash can lose its last changes. synchronous_commit_off the reference
wal_sender_timeout is shorter than a minute. wal_sender_timeout_short the reference