| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: parallelizing the archiver |
| Date: | 2021-10-22 23:34:25 |
| Message-ID: | CA+TgmobV4dsx5oWZ5izfcGVM3Q0Vq2Byr=_Oq4quqdhYgQvW=A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 22, 2021 at 1:42 PM Bossart, Nathan <bossartn(at)amazon(dot)com> wrote:
> Another approach would be to add a new initialization function (e.g.,
> PG_archive_init()) that would be used if the library is being loaded
> from archive_library. Like before, you can use the library for both
> shared_preload_libraries and archive_library, but your initialization
> logic would be expected to go in separate functions. However, there
> still wouldn't be anything forcing that. A library could still break
> the rules and do everything in _PG_init() and be loaded via
> shared_preload_libraries.
I was imagining something like what logical decoding does. In that
case, you make a _PG_output_plugin_init function and it returns a
table of callbacks. Then the core code invokes those callbacks at the
appropriate times.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-10-22 23:48:13 | Re: pg_dump versus ancient server versions |
| Previous Message | Tom Lane | 2021-10-22 23:30:25 | Re: pg_dump versus ancient server versions |