| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'João Rito' <joaovictor(dot)rito(at)gmail(dot)com>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: [PATCH] Explain what the default output_plugin_libraries do |
| Date: | 2026-11-11 05:53:25 |
| Message-ID: | OS7PR01MB183175E7A6F46085258F7028EF5712@OS7PR01MB18317.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi João,
Thanks for sending a comment! For now let's focusing on the doc patch.
> One
> small wording point: "An output plugin must be installed as a
> dynamically loadable library" is not true for the built-in pgoutput,
> so maybe "A custom output plugin" or "An output plugin that is not
> built in".
Hmm, I felt that the wording is correct. IIUC a shared library pgoutput.so must
be installed on the dynamically loadable library. I locally removed the .so then
tried to create a slot, got the below error.
```
postgres=# SELECT * FROM pg_create_logical_replication_slot('test', 'pgoutput');
ERROR: could not access file "pgoutput": No such file or directory
```
Can you clarify bit more if you mention the different point? Or can you share me
what you tested?
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2026-11-11 05:57:55 | RE: [PATCH] Explain what the default output_plugin_libraries do |
| Previous Message | Manu | 2026-11-11 05:40:00 | Re: Assertion failure in WAL summarizer |