Thread

  1. psql tab completion for user functions and if explicitly required also "pg_"

    Florin Irion <irionr@gmail.com> — 2026-02-12T12:19:12Z

    Hello,
    
    I think it would be nice to have tab completion for user functions after 
    `SELECT`, and also for `pg_` in some cases. There was already a 
    discussion around this here 
    https://www.postgresql.org/message-id/CACLU5mQBYaMgGzJ-ZoG4MrBuXLsREcQbiY4pqsnYjMaMQP6hQg%40mail.gmail.com , 
    however as that discussion is ~ 1 year old I thought it's better to 
    start a new one.
    
    Attaching a patch, keeping in mind some doubts that were expressed in 
    the old discussion.
    
    
    Cheers,
    
    Florin Irion
    https://www.enterprisedb.com
  2. Re: psql tab completion for user functions and if explicitly required also "pg_"

    Mario Gonzalez <gonzalemario@gmail.com> — 2026-06-30T18:28:14Z

    On Tue, 30 Jun 2026 at 14:22, Florin Irion <irionr@gmail.com> wrote:
    >
    > Hello,
    >
    > I think it would be nice to have tab completion for user functions after
    > `SELECT`, and also for `pg_` in some cases. There was already a
    > discussion around this here
    > https://www.postgresql.org/message-id/CACLU5mQBYaMgGzJ-ZoG4MrBuXLsREcQbiY4pqsnYjMaMQP6hQg%40mail.gmail.com ,
    > however as that discussion is ~ 1 year old I thought it's better to
    > start a new one.
    >
    > Attaching a patch, keeping in mind some doubts that were expressed in
    > the old discussion.
    >
    
    It needed a rebase. Also, the patch didn't apply directly, I fixed the
    offset and there was a corruption in the file I couldn't fix.
    
    $ git am ~/Downloads/v1-0001-Add-function-name-tab-completion-after-SELECT-in-.patch
    Applying: Add function name tab completion after SELECT in psql
    error: corrupt patch at line 30
    Patch failed at line 30.
    
    In the end, after I fixed the offset, I applied the commit by hand,
    committed the change and squashed it into a single commit to produce
    the patch again.
    Let me know please if you find any errors. I'll check into the code
    now, this was my first attempt to only rebase into latest changes and
    make cfboot hopefully happy.
    
    >
    > Cheers,
    >
    > Florin Irion
    > https://www.enterprisedb.com
    
    
    
    -- 
    Mario Gonzalez
    EDB: https://www.enterprisedb.com
    
  3. Re: psql tab completion for user functions and if explicitly required also "pg_"

    Mario Gonzalez <gonzalemario@gmail.com> — 2026-06-30T20:54:02Z

    On Tue, 30 Jun 2026 at 14:28, Mario González Troncoso
    <gonzalemario@gmail.com> wrote:
    >
    >
    > It needed a rebase. Also, the patch didn't apply directly, I fixed the
    > offset and there was a corruption in the file I couldn't fix.
    >
    > $ git am ~/Downloads/v1-0001-Add-function-name-tab-completion-after-SELECT-in-.patch
    > Applying: Add function name tab completion after SELECT in psql
    > error: corrupt patch at line 30
    > Patch failed at line 30.
    >
    > In the end, after I fixed the offset, I applied the commit by hand,
    > committed the change and squashed it into a single commit to produce
    > the patch again.
    > Let me know please if you find any errors. I'll check into the code
    > now, this was my first attempt to only rebase into latest changes and
    > make cfboot hopefully happy.
    >
    > >
    
    I noticed a syntax error and the change was passing the local tests
    because I didn't enable the TAP tests. Fixing the syntax error I
    introduced and passing the tests locally, this time with TAP tests
    enabled.
    
    -- 
    Mario Gonzalez
    EDB: https://www.enterprisedb.com
    
  4. Re: psql tab completion for user functions and if explicitly required also "pg_"

    Florin Irion <irionr@gmail.com> — 2026-07-03T13:56:53Z

    
    On 30/06/2026 22:54, Mario González Troncoso wrote:
    > I noticed a syntax error and the change was passing the local tests
    > because I didn't enable the TAP tests. Fixing the syntax error I
    > introduced and passing the tests locally, this time with TAP tests
    > enabled.
    Mario, thanks for checking on this!
    I left it a bit behind because I hadn't any feedback, so not sure if 
    people want it.
    
    Let me know if the implementation makes sense.
    
    Cheers,
    Florin
    www.enterprisedb.com