From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: More new SQL/JSON item methods |
Date: | 2024-01-18 15:49:11 |
Message-ID: | e255ecf4-3fb7-4bdf-8ad9-81450514fa37@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 18.01.24 15:25, Jeevan Chalke wrote:
> Peter, I didn't understand why the changes you did in your 0002 patch
> were required here. I did run the pgindent, and it didn't complain to
> me. So, just curious to know more about the changes. I have not merged
> those changes in this single patch. However, if needed it can be cleanly
> applied on top of this single patch.
I just thought it was a bit wasteful with vertical space. It's not
essential.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2024-01-18 15:50:13 | Re: Emit fewer vacuum records by reaping removable tuples during pruning |
Previous Message | Tom Lane | 2024-01-18 15:46:46 | Re: Increasing IndexTupleData.t_info from uint16 to uint32 |