Re: vacuumdb changes for stats import/export - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: vacuumdb changes for stats import/export
Date
Msg-id Z8XXEYfbSatGrrty@nathan
Whole thread Raw
In response to Re: vacuumdb changes for stats import/export  (John Naylor <johncnaylorls@gmail.com>)
Responses Re: vacuumdb changes for stats import/export
List pgsql-hackers
On Mon, Mar 03, 2025 at 05:58:43PM +0700, John Naylor wrote:
> On Sat, Mar 1, 2025 at 3:42 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
>> On Thu, Feb 27, 2025 at 04:36:04PM +0700, John Naylor wrote:
>> > I had to read it several times before I noticed the difference between
>> > "* found_objs" and "*found_objs". Maybe some extra spacing and breaks
>> > would help, or other reorganization.
>>
>> Yeah, it's pretty atrocious.  I think the main problem is that the
>> interface is just too complicated, so I'll take a step back and see if I
>> can make it more understandable to humans.
> 
> The interface is awkward, but on the other hand only a small part has
> to really know about it. It's worth trying to make it more readable if
> you can.

True.  One small thing we could do is to require "found_objs" (the double
pointer) to always be non-NULL, but that just compels some callers to
provide otherwise-unused variables.  I've left the interface alone for now.

>> In the meantime, here's an attempt at adjusting the comment:
> 
> That's better, and if we end up with this interface, we'll want quotes
> around the names so the eye can tell where the "*" belong.

I did that in v3.  I also tried to break up this comment into bullet points
for better separation and logical flow.

-- 
nathan

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: bug when apply fast default mechanism for adding new column over domain with default value
Next
From: Nathan Bossart
Date:
Subject: Re: PATCH: warn about, and deprecate, clear text passwords