Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless)

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Daniel Verite <daniel(at)manitou-mail(dot)org>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless)
Date: 2017-01-24 18:40:26
Message-ID: CADkLM=fHZufaTG+Pd7einhCe77xmv6n2i2=pzo+FFX5LHx1hoQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 24, 2017 at 1:25 PM, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
wrote:

> This might be asking a lot, but could we make a "strict" mode for
> ParseVariableBool() that returns a success boolean, and have the existing
> ParseVariableBool() signature call that new function, and issue the
> "assuming " warning if the strict function failed?

Nevermind. Looking at the v7 patch I see that it does everything I need and
more. I should have looked first.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2017-01-24 18:57:26 Re: pgbench more operators & functions
Previous Message Alvaro Herrera 2017-01-24 18:36:13 Re: lseek/read/write overhead becomes visible at scale ..