| From: | a(dot)imamov(at)postgrespro(dot)ru |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Custom connstr in background_psql() |
| Date: | 2024-09-19 13:00:30 |
| Message-ID: | 8287b73a7a573d64c5dd3a905f82670c@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier писал(а) 2024-09-18 01:57:
> On Wed, Sep 18, 2024 at 01:08:26AM +0300, a(dot)imamov(at)postgrespro(dot)ru
> wrote:
>> I've noticed that there is no way to specify a custom connection
>> string when
>> calling the PostgreSQL::Test::Cluster->background_psql() method
>> compared to the
>> PostgreSQL::Test:Cluster->psql(). It seems useful to have this feature
>> while
>> testing with BackgroundPsql, for example, when the default host value
>> needs
>> to be overridden to establish different types of connections.
>>
>> What do you think?
>
> I think that it makes sense to extend the routine as you are
> suggesting. At least I can see myself using it depending on the test
> suite I am dealing with. So count me in.
> --
> Michael
Should I register the proposal in CF?
Which one to choose if so?
--
regards,
Aidar Imamov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-09-19 13:25:05 | Re: pgsql: Don't enter parallel mode when holding interrupts. |
| Previous Message | Florents Tselai | 2024-09-19 12:57:00 | Re: [PATCH] WIP: replace method for jsonpath |