From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Higuchi, Daisuke" <higuchi(dot)daisuke(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [Bug fix]If recovery.conf has target_session_attrs=read-write, the standby fails to start. |
Date: | 2017-05-20 00:27:54 |
Message-ID: | CAB7nPqTmym5t-X6hvMF_P-KRc=ndXtbQCTiU=NhS_jvL7x1kCA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 20, 2017 at 5:32 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> We'd probably be better off to implement case-insensitivity the hard way.
> There is a reason why none of our other flex scanners use this switch.
Do you think that it would be better to list the letter list for each
keyword in repl_scanner.l or have something more generic? As not that
many commands are added in the replication protocol, I would think
that this is more than enough for each command, say:
[Ss][Ll][Oo][Tt] { return K_SLOT; }
etc.
> While I'm whining ... it looks like the other flex options selected here
> were cargo-culted in rather than being thought about. Surely we don't
> run syncrep_scanner often enough, nor over so much data, that it's a
> good tradeoff to use the options for larger tables.
Indeed, good catch.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-05-20 00:49:00 | Re: [Bug fix]If recovery.conf has target_session_attrs=read-write, the standby fails to start. |
Previous Message | Thomas Munro | 2017-05-20 00:01:08 | Re: transition table behavior with inheritance appears broken (was: Declarative partitioning - another take) |