| From: | pgsql-admin(at)kolttonen(dot)fi |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: The current shape of PG master-slave replication |
| Date: | 2018-11-16 05:03:45 |
| Message-ID: | alpine.LFD.2.21.1811160701360.25223@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, 15 Nov 2018, Payal Singh wrote:
> It is more reliable than default MySQL replication. Default MySQL
> replication is logical whereas default postgres replication is binary. In
> the crudest of terms, if something goes wrong you can't just 'skip'
> statements in postgres to get replication to work like you can in MySQL.
> This ensures better data integrity during replication. As for non-defaults,
> pg10 and onwards support logical replication as well, with the usual
> caveats that logical replication comes with in any database.
I see. Thanks for that explanation.
I really have to study these DB things a bit more in order to gain better
understanding of replication's basic models and structure.
Best regards,
Unto Sten
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios | 2018-11-16 08:18:07 | Re: PostgreSQL 10.5 : Logical replication timeout results in PANIC in pg_wal "No space left on device" |
| Previous Message | pgsql-admin | 2018-11-16 05:01:27 | Re: The current shape of PG master-slave replication |