[wp-trac] [WordPress Trac] #60375: Site Transfer Protocol
WordPress Trac
noreply at wordpress.org
Mon Jan 12 12:00:24 UTC 2026
#60375: Site Transfer Protocol
-------------------------+------------------------------
Reporter: zieladam | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Import | Version:
Severity: normal | Resolution:
Keywords: | Focuses:
-------------------------+------------------------------
Comment (by nickchomey):
Very ambitious proposal here! I have one question related to the most
recent comment.
Replying to [comment:36 zieladam]:
> Earlier this year, @dmsnell investigated hooking into MySQL binary
replication log for data indexing purposes and ran into some blockers.
I've asked him today what were the blockers and this is what he said:
>
> > two things: we couldn’t control getting it connected on all the
various hosts; and I thought it didn’t provide all the data we wanted
anyway (e.g. from UPDATE queries that don’t specify ids)
Could you please elaborate on what the concern/limitation is here? I've
done a lot of work with binlog replication and have never come across
anything like this. After all, the binlog is the native way that any
replication (including bidirectional syncing, eg with Galera) is done. If
it was missing data, how would any replication be possible...?
In fact, apart from just a full dump via mysqldump, xtrabackup etc, I
consider using the binlog as perhaps the only reliable way to do anything
like this - you'd essentially be re-implementing it with any other
approach.
Exposing/leveraging the binlog would make it relatively simple to use with
a variety of other powerful tools, like CDC ETL pipelines. Debezium is the
gold standard for anything like this - I wasted far too much time on other
niche tools before accepting the JVM into my life.
To the extent that enabling the binlog and making it accessible on all
hosts would be impractical, that could just become another differentiating
factor when choosing hosts? Catering to the lowest common denominator
holds back progress.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/60375#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list