From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Detailed release notes |
Date: | 2024-09-18 14:46:23 |
Message-ID: | 1811332.1726670783@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> writes:
> Em qua., 18 de set. de 2024 às 06:02, Peter Eisentraut <peter(at)eisentraut(dot)org>
> escreveu:
>> Maybe this shouldn't be done between RC1 and GA. This is clearly a more
>> complex topic that should go through a proper review and testing cycle.
> I think this is just a question of decision, not reviewing or testing.
I'd say the opposite: the thing we lack is exactly testing, in the
sense of how non-hackers will react to this. Nonetheless, I'm not
upset about trying to do it now. We will get more feedback about
major-release notes than minor-release notes. And the key point
is that it's okay to consider this experimental. Unlike say a SQL
feature, there are no compatibility concerns that put a premium on
getting it right the first time. We can adjust the annotations or
give up on them without much cost.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2024-09-18 14:47:45 | Re: Large expressions in indexes can't be stored (non-TOASTable) |
Previous Message | Benoit Lobréau | 2024-09-18 14:46:00 | Re: Logging parallel worker draught |