Re: specifying multiple options in URI psql behaviour?

From: Wim Bertels <wim(dot)bertels(at)ucll(dot)be>
To: "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: specifying multiple options in URI psql behaviour?
Date: 2023-10-02 15:21:33
Message-ID: d22e148fdc6cc02e47e4e28d63ed88eb30548ae6.camel@ucll.be
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane schreef op ma 02-10-2023 om 10:21 [-0400]:
> Wim Bertels <wim(dot)bertels(at)ucll(dot)be> writes:
> > * but if you put more than 1 option, then it doesn't?:
>
> > #psql
> > postgresql://myuser(at)myserver/mydb?connect_timeout=10&target_session
> > _attrs=any
>
> Maybe you forgot to quote that?  Ampersand is a shell metacharacter.

yes indeed, & bg and fg, thank you Tom

# psql
'postgresql://myuser(at)myserver/mydb?connect_timeout=10&target_session_at
trs=any'

or just

# psql
postgresql://myuser(at)myserver/mydb?connect_timeout=10'&'target_session_a
ttrs=any

>
> (It does seem to work for me, as long as I put quotes around the
> URL.)
>
>                         regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2023-10-02 16:10:49 Re: pg_agent jobs
Previous Message Ron 2023-10-02 14:59:41 Re: Operating of synchronous master when no standby is available