| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: POC: enable logical decoding when wal_level = 'replica' without a server restart |
| Date: | 2025-10-22 09:28:38 |
| Message-ID: | CAA4eK1JNwVPPYBeG4waLzEM3mdsMLXq3_QvoqJ5gjt40M61Drw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 22, 2025 at 2:40 PM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
>
> On Fri, Oct 17, 2025 at 11:09 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> >
>
> I want to discuss the create-publication case, which currently gives
> this warning:
>
> postgres=# create publication pub1 for all tables;
> WARNING: logical decoding should be allowed to publish logical changes
> HINT: Before creating subscriptions, set "wal_level" >= "logical" or
> create a logical replication slot when "wal_level" = "replica".
> CREATE PUBLICATION
>
> But is this warning really necessary during publication creation?
>
On HEAD, the WARNING/HINT is as follows for the above case:
WARNING: "wal_level" is insufficient to publish logical changes
HINT: Set "wal_level" to "logical" before creating subscriptions.
Shouldn't we simply change the HINT to "Set "wal_level" to "logical"
or create a logical replication slot before creating subscriptions."?
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Waizenegger | 2025-10-22 09:32:25 | Re: [PATCH] pg_get_domain_ddl: DDL reconstruction function for CREATE DOMAIN statement |
| Previous Message | Richard Guo | 2025-10-22 09:25:36 | Issue with query_is_distinct_for() and grouping sets |