Re: specifying multiple options in URI psql behaviour? - Mailing list pgsql-general

From Ron
Subject Re: specifying multiple options in URI psql behaviour?
Date
Msg-id 5440513c-9d1b-8b45-9023-e2ebc97b6d19@gmail.com
Whole thread Raw
In response to Re: specifying multiple options in URI psql behaviour?  (Wim Bertels <wim.bertels@ucll.be>)
List pgsql-general
On 10/2/23 10:21, Wim Bertels wrote:
> Tom Lane schreef op ma 02-10-2023 om 10:21 [-0400]:
>> Wim Bertels <wim.bertels@ucll.be> writes:
>>> * but if you put more than 1 option, then it doesn't?:
>>> #psql
>>> postgresql://myuser@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@myserver/mydb?connect_timeout=10&target_session_at
> trs=any'
>
> or just
>
> # psql
> postgresql://myuser@myserver/mydb?connect_timeout=10'&'target_session_a
> ttrs=any

Escaping the & using \ should also work.

-- 
Born in Arizona, moved to Babylonia.



pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: Problems starting slave
Next
From: "Peter J. Holzer"
Date:
Subject: Re: Peer authentication failed ???