Re: Proposal: adding a better description in psql command about large objects - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Proposal: adding a better description in psql command about large objects
Date
Msg-id 20220603143921.GA2624579@nathanxps13
Whole thread Raw
In response to Re: Proposal: adding a better description in psql command about large objects  ("Thibaud W." <thibaud.walkowiak@dalibo.com>)
Responses Re: Proposal: adding a better description in psql command about large objects  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Jun 03, 2022 at 10:12:30AM +0200, Thibaud W. wrote:
> In fact the original tabs were missing in the first file.
> In version v2, it seems interesting to keep calls to the fprintf function
> for translation. I attached a new file.

Yes, it looks like the precedent is to have an fprintf() per command.  I
still think the indentation needs some adjustment for readability.  In the
attached, I've lined up all the large object commands.  This is offset from
most other commands, but IMO this is far easier to read, and something
similar was done for the operator class/family commands.  Thoughts?

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
Next
From: Daniel Gustafsson
Date:
Subject: Re: [v15 beta] pg_upgrade failed if earlier executed with -c switch