Re: specifying multiple options in URI psql behaviour?

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: specifying multiple options in URI psql behaviour?
Date: 2023-10-03 13:35:54
Message-ID: 5440513c-9d1b-8b45-9023-e2ebc97b6d19@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(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

Escaping the & using \ should also work.

--
Born in Arizona, moved to Babylonia.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter J. Holzer 2023-10-03 13:37:36 Re: Peer authentication failed ???
Previous Message Ron 2023-10-03 13:33:12 Re: Problems starting slave