Re: pgsql: Improve error handling in RemovePgTempFiles().

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Improve error handling in RemovePgTempFiles().
Date: 2018-01-08 02:22:25
Message-ID: 30564.1515378145@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> On Mon, Jan 8, 2018 at 2:41 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Hearing no comments, I did it the first way.

> It's funny that the two boolean arguments are always opposite.
> They're essentially both saying "top level?".

Yeah. I thought about using a single "bool top_level" argument instead,
but concluded that this way is clearer and potentially more flexible.
There are other places where we have similar cases of flag arguments
that are redundant in current usage, but we leave it like that for
clarity as to what the function's API spec is.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2018-01-08 13:14:11 Re: pgsql: Implement channel binding tls-server-end-point for SCRAM
Previous Message Thomas Munro 2018-01-08 02:16:08 Re: pgsql: Improve error handling in RemovePgTempFiles().