Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nwseI-0004HC-0r for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Jun 2022 21:46:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nwseF-0003Wh-IL for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Jun 2022 21:46:31 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nwseF-0003UI-6L for pgsql-hackers@lists.postgresql.org; Thu, 02 Jun 2022 21:46:31 +0000 Received: from mail-io1-xd29.google.com ([2607:f8b0:4864:20::d29]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nwseC-0000NI-De for pgsql-hackers@lists.postgresql.org; Thu, 02 Jun 2022 21:46:30 +0000 Received: by mail-io1-xd29.google.com with SMTP id 62so6119002iov.4 for ; Thu, 02 Jun 2022 14:46:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=bQnXYe2dSOPveju4J3GG92qcL/C3pOsvEb6wOP6Q5S0=; b=loHqQW7162MfR1vfNaisJYpD2JRKXXROnVynZ7KofDR+Ya4WgPoTLmEzFiWPE+W0DV 4hLgQmdDPDybq76RaeDH0dWFgyecC/rUYI4T9ZRhwi+fcyl5+C2VxC9B4oZrJhxCeD7U TuNAJPXUoii+y7LaT5gEj3O5Q7t7uGN0IzMGmzxXJ8Gx3q2U9qy1OAMxVLdLNv3Hv/BQ RiPHox6Hcy9bb1zPDL3n3UjLI/+utiboGBx7pyidhUfxtnF49siDFyAA1fS0n4rY9Mbi ljmO8QTYkyUKPiUxfEpNePlKFZFl9sF2NGwi60gEQdJ0kKYktWQkIN7mSVl0u8rsjbMg RFQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=bQnXYe2dSOPveju4J3GG92qcL/C3pOsvEb6wOP6Q5S0=; b=xUuFeJLDHYZQdxDb7QJ4DI0Ts/ZPAElPBeSAL4g35SEgTqt0mkCIBjoxchgKdk32rY Ra0sOsrA1+ZVh+wV5sfD6Raq+su0yOr3mEON3NR/GA1eTML7w1zj+3IFLLscnxD+fpU0 eHAYzHxtthfnXCeULo4wxK8i9rbCIimEE+G3JFLQOvSBHl5ZifF4suOaTqba8VaieaES OAnXOL7LLSSRvuwoLTIiLhyf0KDHU9Lt6xozp15SJWj+ZYBDc7sdRa8jyBZqvVna8LcA p9V7lJvGtCaz7EgH1SO45as+SknL2Q5/psS5MT+Uiipl+LAG0WixZWP26wh+zAaqzDvD Adaw== X-Gm-Message-State: AOAM5316Tj8fwijEZqJBvA4MQzWXpmPxKI9TFONCYdChJWG1MzQDvd0A CZNbKgFYUOj8A3UXj1MjKPBTKzzXjyQ= X-Google-Smtp-Source: ABdhPJwEwhjYlSSIDdEf2ZgDP4jVv4GZn01ZQE1gNXaUO+ZPZD1YMK565ElNmdepckPAj607bWFc1w== X-Received: by 2002:a6b:3f03:0:b0:65a:4236:bb3e with SMTP id m3-20020a6b3f03000000b0065a4236bb3emr3526807ioa.194.1654206387468; Thu, 02 Jun 2022 14:46:27 -0700 (PDT) Received: from nathanxps13 ([2600:1700:48f8:340f:8a13:90a6:f5c4:9c43]) by smtp.gmail.com with ESMTPSA id l9-20020a056e02066900b002d18e3dcb67sm1888162ilt.46.2022.06.02.14.46.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Jun 2022 14:46:26 -0700 (PDT) Date: Thu, 2 Jun 2022 14:46:25 -0700 From: Nathan Bossart To: "Thibaud W." Cc: pgsql-hackers@lists.postgresql.org Subject: Re: Proposal: adding a better description in psql command about large objects Message-ID: <20220602214625.GA2494933@nathanxps13> References: <43f0439c-df3e-a045-ac99-af33523cc2d4@dalibo.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="/04w6evG8XlLl3ft" Content-Disposition: inline In-Reply-To: <43f0439c-df3e-a045-ac99-af33523cc2d4@dalibo.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jun 02, 2022 at 11:12:46AM +0200, Thibaud W. wrote: > Attached is a small patch to add a description to the meta commands > regarding > large objects. This seems reasonable to me. Your patch wasn't applying for some reason, so I created a new one with a commit message and some small adjustments. What do you think? -- Nathan Bossart Amazon Web Services: https://aws.amazon.com --/04w6evG8XlLl3ft Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="v2-0001-Add-descriptions-for-psql-s-large-object-backslas.patch" From ca23b5c3b1ad3af4c47bb6d438c58a6e3ba5a1b6 Mon Sep 17 00:00:00 2001 From: Nathan Bossart Date: Thu, 2 Jun 2022 14:35:31 -0700 Subject: [PATCH v2 1/1] Add descriptions for psql's large object backslash commands. These should be mostly self-explanatory, but they are the only backslash commands lacking individual short descriptions. Author: Thibaud W. Reviewed by: Nathan Bossart Description: https://postgr.es/m/43f0439c-df3e-a045-ac99-af33523cc2d4%40dalibo.com --- src/bin/psql/help.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/bin/psql/help.c b/src/bin/psql/help.c index 49eb116f33..54580ac928 100644 --- a/src/bin/psql/help.c +++ b/src/bin/psql/help.c @@ -321,10 +321,10 @@ slashUsage(unsigned short int pager) fprintf(output, "\n"); fprintf(output, _("Large Objects\n")); - fprintf(output, _(" \\lo_export LOBOID FILE\n" - " \\lo_import FILE [COMMENT]\n" - " \\lo_list[+]\n" - " \\lo_unlink LOBOID large object operations\n")); + fprintf(output, _(" \\lo_export LOBOID FILE export large object to file\n" + " \\lo_import FILE [COMMENT] import large object from file\n" + " \\lo_list[+] list large objects\n" + " \\lo_unlink LOBOID delete a large object\n")); ClosePager(output); } -- 2.25.1 --/04w6evG8XlLl3ft--