pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Nico Williams <nico@cryptonector.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Isaac Morland <isaac.morland@gmail.com>
Cc: Jeff Davis <pgsql@j-davis.com>
Cc: Chapman Flack <chap@anastigmatix.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Pre-proposal: unicode normalized text
Date: Fri, 6 Oct 2023 13:25:44 -0500
Message-ID: <ZSBRKFJ+gy5iUXxa@ubby21> (raw)
In-Reply-To: <CA+TgmoYGrrOOahgxNO=W7_cvG-g--WVtuK6SYkWa+PEDdTOUqw@mail.gmail.com>
References: <CA+TgmoY6vNbDoBugDT=3rdJ-diyLw-kQ9sxB2JXenv48xV_tVQ@mail.gmail.com>
	<43864caecd65d02081d623d05ccc1683@anastigmatix.net>
	<CAMsGm5eyegAkb2Eq+8d2j+BxDnSZXH0AUciwi6rA60V_ft=1dw@mail.gmail.com>
	<94a0e631b787d56fec1b17e03fe045b5e14907c1.camel@j-davis.com>
	<CAMsGm5f8k4_C6VuerSbF2gXeVwD9kMZQk43kO85Oi4oGVL7EMA@mail.gmail.com>
	<CA+TgmobAxizsgjxvZdEQxjEs6RA3qu7JLti_LdXtaXODJoWzNw@mail.gmail.com>
	<ZR8LLrk9AJVxEFbX@ubby21>
	<CA+TgmoaF_KHkgcisLFaKzR_husGtAOnjEez9biH2QHyX-4dAyA@mail.gmail.com>
	<ZSBGJalw0ytQ63Sz@ubby21>
	<CA+TgmoYGrrOOahgxNO=W7_cvG-g--WVtuK6SYkWa+PEDdTOUqw@mail.gmail.com>

On Fri, Oct 06, 2023 at 02:17:32PM -0400, Robert Haas wrote:
> On Fri, Oct 6, 2023 at 1:38 PM Nico Williams <nico@cryptonector.com> wrote:
> > On Fri, Oct 06, 2023 at 01:33:06PM -0400, Robert Haas wrote:
> > > On Thu, Oct 5, 2023 at 3:15 PM Nico Williams <nico@cryptonector.com> wrote:
> > > > Text+encoding can be just like bytea with a one- or two-byte prefix
> > > > indicating what codeset+encoding it's in.  That'd be how to encode
> > > > such text values on the wire, though on disk the column's type should
> > > > indicate the codeset+encoding, so no need to add a prefix to the value.
> > >
> > > Well, that would be making the encoding a per-value property, rather
> > > than a per-column property like collation as I proposed. I can't see
> >
> > On-disk it would be just a property of the type, not part of the value.
> 
> I mean, that's not how it works.

Sure, because TEXT in PG doesn't have codeset+encoding as part of it --
it's whatever the database's encoding is.  Collation can and should be a
porperty of a column, since for Unicode it wouldn't be reasonable to
make that part of the type.  But codeset+encoding should really be a
property of the type if PG were to support more than one.  IMO.





view thread (77+ messages)  latest in thread

Message-ID: <ZSBRKFJ+gy5iUXxa@ubby21>
Permalink:  ../ZSBRKFJ+gy5iUXxa@ubby21/
Also on:    postgresql.org/message-id/ZSBRKFJ+gy5iUXxa@ubby21

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: nico@cryptonector.com, robertmhaas@gmail.com, isaac.morland@gmail.com, pgsql@j-davis.com, chap@anastigmatix.net
  Subject: Re: Pre-proposal: unicode normalized text
  In-Reply-To: <ZSBRKFJ+gy5iUXxa@ubby21>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox