| From: | a(dot)imamov(at)postgrespro(dot)ru |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Custom connstr in background_psql() |
| Date: | 2024-09-17 22:08:26 |
| Message-ID: | ecacb079efc533aed3c234cbcb5b07b6@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi, hackers!
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?
| Attachment | Content-Type | Size |
|---|---|---|
| background_psql.patch | text/x-diff | 1.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2024-09-17 22:14:46 | Re: Adding skip scan (including MDAM style range skip scan) to nbtree |
| Previous Message | Sami Imseih | 2024-09-17 22:01:18 | Re: query_id, pg_stat_activity, extended query protocol |