From: | Jeremy Finzel <finzelj(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Review of DDL replication solution |
Date: | 2017-08-09 13:14:22 |
Message-ID: | CAMa1XUgEjn1B6CfbQGZ5zUietmnVv_vEqqs-fHnr=fdqapC+qg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello!
I am new to Postgres backend development, and have created a recent project
that has minimal C code. It is a transparent DDL replication solution
built on top of pglogical, but with a concept that could be used also with
other logical replication solutions if they support some mechanism to
propagate SQL to subscribers. I describe some of its limitations in the
docs:
https://github.com/enova/pgl_ddl_deploy
I would greatly appreciate some critique/review of the C code in
particular:
https://github.com/enova/pgl_ddl_deploy/blob/master/pgl_ddl_deploy.c
It is extremely simple and most of the code is shared from other existing
Postgres code. But if we put this into production, I'd love for some more
experienced devs to at least take a look at it.
Likewise, I would love if in general anyone would try to see if using this
is feasible in their environment.
I have posted already on the bdr/pglogical list, but would also like to
share this with the broader community.
I appreciate all positive/negative feedback. Cheers!
Jeremy Finzel
(DBA at Enova International)
From | Date | Subject | |
---|---|---|---|
Next Message | Haribabu Kommi | 2017-08-09 13:21:30 | Re: parallelize queries containing initplans |
Previous Message | Haribabu Kommi | 2017-08-09 12:59:13 | Re: parallelize queries containing initplans |