Postgres Pro
Downloads
Home   >   mailing lists

Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless) - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless)
Date
Msg-id CADkLM=fHZufaTG+Pd7einhCe77xmv6n2i2=pzo+FFX5LHx1hoQ@mail.gmail.com
Whole thread Raw
In response to Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless)  (Corey Huinker <corey.huinker@gmail.com>)
List pgsql-hackers
Tree view

On Tue, Jan 24, 2017 at 1:25 PM, Corey Huinker <corey.huinker@gmail.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.

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] lseek/read/write overhead becomes visible at scale ..
Next
From: "David G. Johnston"
Date:
Subject: Re: [HACKERS] pgbench more operators & functions