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

From Wim Bertels
Subject Re: specifying multiple options in URI psql behaviour?
Date
Msg-id d22e148fdc6cc02e47e4e28d63ed88eb30548ae6.camel@ucll.be
Whole thread Raw
In response to Re: specifying multiple options in URI psql behaviour?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: specifying multiple options in URI psql behaviour?
List pgsql-general
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

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


pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: Operating of synchronous master when no standby is available
Next
From: Adrian Klaver
Date:
Subject: Re: pg_agent jobs