[pgpool-hackers: 4441] Re: Guard against ill mannered frontend

[Tatsuo Ishii]

>> So my proposal is, guarding against such a ill-mannerd message
>> sequence and throwing an error to terminate the session if such
>> messages are recieved.
>> 
>> Here are details of the proposal:
>> 
>> 1) add a switch to turn on the "safe guard". This implies that the
>>    feature is only implemented on master branch. Others may argue that
>>    this should be back-patched.
>> 
>> 2) if such a violation is detected, raise an error and terminate the
>>    session. Continuing the session will be better but it's hard to
>>    implement and I think it's not worth the trouble.
> 
> Regarding #1, I started to think that creating a new switch does not
> make much sense. If the switch is off, a session could hang which is
> the worst experience for users. So it seems there's no choice other
> than turning on the switch. If the switch is always on, why we need
> the switch?
> 
> I am going to commit only #2 part.

commit & pushed to master branch.
https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=240c668d120065534b1d298d6facc86839fcbab9

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp