On Monday, August 4, 2025, Álvaro Herrera wrote:
> On 2025-Jul-31, David G. Johnston wrote:
>
> > > On Thu, Jul 31, 2025 at 8:05 PM Magnus Hagander
> > > wrote:
>
> > > > I can agree that the "will likely be removed" is a bad wording, and
> > > > clearly it was wrong :)
>
> I disagree that this
On 2025-Jul-31, Shuyu Pan wrote:
> I like your versions that emphasize: don’t drop the constraint in the
> same alter table set no null command. Similar to David’s point, I
> spent some time trying to figure out a simple refactoring to carry the
> optimization all the way to the end but it might
Thanks a lot Álvaro for preparing the clarification so quickly. Looking forward
to the release.
If we mark a column to skip table scan during drop (phase 0) and later skip the
table scan when setting attributes (phase 7), we will not risk data corruption
if the Access Exclusive lock is never rel
On Mon, 2025-08-04 at 12:30 +0700, Oleg Tselebrovskiy wrote:
> First patch just adds this warning about not relying on initcap()
> exact
> result. The second one is the same, but removes the part "what is a
> word"
> since it's could be moot because we recommend writing custom
> functions,
> so un
On 2025-Jul-31, David G. Johnston wrote:
> > On Thu, Jul 31, 2025 at 8:05 PM Magnus Hagander
> > wrote:
> > > I can agree that the "will likely be removed" is a bad wording, and
> > > clearly it was wrong :)
I disagree that this was clearly wrong -- you just haven't seen that
future yet. It do
