From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Lucas Viecelli <lviecelli199(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: warning to publication created and wal_level is not set to logical |
Date: | 2019-07-10 00:47:08 |
Message-ID: | 8402.1562719628@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> New status: Ready for Committer. If nobody wants to bikeshed the
> wording or other details, I will commit this tomorrow.
Hm, so:
1.
+ errmsg("insufficient wal_level to publish logical changes"),
Might read better as "wal_level is insufficient to publish logical changes"?
2.
+ errhint("Set wal_level to logical before creating subscriptions")));
This definitely is not per style guidelines, needs a trailing period.
3. AFAICS, the proposed test case changes will cause the core regression
tests to fail if wal_level is not replica. This is not true today ---
they pass regardless of wal_level --- and I object in the strongest terms
to making it otherwise.
I'm not really convinced that we need regression tests for this change at
all, but if we do, put them in one of the TAP replication test suites,
which already depend on wal_level being set to something in particular.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2019-07-10 00:58:40 | Re: Extending PostgreSQL with a Domain-Specific Language (DSL) - Development |
Previous Message | Thomas Munro | 2019-07-10 00:46:25 | coypu: "FATAL: sorry, too many clients already" |