| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Neha Khatri <nehakhatri5(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: wal_level > WAL_LEVEL_LOGICAL |
| Date: | 2017-05-24 12:29:15 |
| Message-ID: | CA+TgmoavskoSKMfuOx-YTDavjuuPoYVLCN7PUq3W=m4vHxzjEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 22, 2017 at 9:08 AM, Neha Khatri <nehakhatri5(at)gmail(dot)com> wrote:
> As per my understabding, current postgres server supports only three
> values for wal_level i.e. 'minimal' , 'replica' or 'logical'. But
> following error message brought to notice that there are various code
> spots that try to look for wal_level >= WAL_LEVEL_LOGICAL:
I suspect that this was intended as future-proofing. I think it's
actually very reasonable to write the internal tests that way, but it
does seem strange that it's crept into the user-visible error
messages.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-05-24 12:44:32 | Re: Broken hint bits (freeze) |
| Previous Message | Robert Haas | 2017-05-24 12:26:24 | Re: Index created in BEFORE trigger not updated during INSERT |