| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu>, Erik Rijkers <er(at)xs4all(dot)nl>, Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers-owner(at)postgresql(dot)org |
| Subject: | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |
| Date: | 2017-03-01 04:02:55 |
| Message-ID: | CADkLM=eLwZHnK82E=qtLMxWy_UDJe-XUMUK1xABPgSP386H4Qw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
>
>>
>> Alternatively if the structure must really be kept, then deal with errors
>> in a first switch, read value *after* switch and deal with other errors
>> there, then start a second switch, and adjust the documentation accordingly?
>>
>> switch
>> errors
>> read
>> if
>> errors
>> // no error
>> switch
>>
>
>
it's now something more like
switch
error-conditions
if no-errors
read
if was a boolean
switch last-state
It doesn't strike me as much cleaner, but it's no worse, either.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001.if_endif.v19.diff | text/plain | 32.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kuntal Ghosh | 2017-03-01 04:03:07 | Re: Performance degradation in TPC-H Q18 |
| Previous Message | Andres Freund | 2017-03-01 04:02:22 | Re: Performance degradation in TPC-H Q18 |