From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Small TAP improvements |
Date: | 2022-11-14 15:18:47 |
Message-ID: | 6cb54881-9a3b-d0df-880a-1cc61e507a9e@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2022-11-09 We 05:35, Andrew Dunstan wrote:
> On 2022-11-06 Su 08:51, Álvaro Herrera wrote:
>> On 2022-Jun-14, Andrew Dunstan wrote:
>>
>>> OK, here's a more principled couple of patches. For config_data, if you
>>> give multiple options it gives you back the list of values. If you don't
>>> specify any, in scalar context it just gives you back all of pg_config's
>>> output, but in array context it gives you a map, so you should be able
>>> to say things like:
>>>
>>> my %node_config = $node->config_data;
>> Hi, it looks to me like these were forgotten?
>>
> Yeah, will get to it this week.
>
>
> Thanks for the reminder.
>
>
Pushed now.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-11-14 15:41:29 | Re: Add sub-transaction overflow status in pg_stat_activity |
Previous Message | Robert Haas | 2022-11-14 15:09:57 | Re: Add sub-transaction overflow status in pg_stat_activity |