Re: CREATE DATABASE command for non-libc providers

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Daniel Verite <daniel(at)manitou-mail(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CREATE DATABASE command for non-libc providers
Date: 2025-06-13 16:50:12
Message-ID: 228fb1114ecf63cddfda84a8d74c07d77814c15d.camel@j-davis.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2025-06-13 at 18:41 +0200, Daniel Verite wrote:
> > The main challenge is backwards compatibility.
> Why would it be that bad?
> FTS indexes don't get corrupted that way. You may get different
> lexems before and after the upgrade for some documents, and then
> what?

It would produce different results than if you started from scratch in
v19. It's hard for me to say whether that would be acceptable or not,
but I could see how that could be confusing to users if they notice.
Perhaps release notes are enough?

> The FTS parser had seen user-visible changes in the past, and
> regenerating tsvectors because of that were merely a suggestion.

Interesting, thank you for looking into the history here. It would
certainly be simpler to just make FTS fully collation-aware.

Regards,
Jeff Davis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2025-06-13 17:08:43 Re: Reduce TupleHashEntryData struct size by half
Previous Message Daniel Verite 2025-06-13 16:41:45 Re: CREATE DATABASE command for non-libc providers