From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Alexander Borisov <lex(dot)borisov(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal to add a new URL data type. |
Date: | 2024-12-11 16:34:31 |
Message-ID: | CA+TgmobjN7nSAR0dBMmv2NgVH130uwBVxd-Bbg1zyOXeqiBSNw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Dec 6, 2024 at 8:46 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> A URL datatype is a *good idea* but one which I personally believe is best
> handled as an external extension.
+1. I don't think that it's an intrinsically bad idea to have a URL
data type in the core distribution, but no compelling reason for
putting it there has been proposed. Alexander's effort can equally
well live in github or pgxn or whatever and people who want to use it
still can. Also, it's pretty clear from reading this thread that
there's more than one way to do this and not everybody agrees with or
likes the particular thing Alexander has done. For an out-of-core
extension, that's perfectly fine, and even good: different people want
different things, and that's OK. For something that's part of
PostgreSQL itself, it's a big problem. There's no reason that we
should privilege one implementation over others, and we certainly do
not want the core project to have to maintain and ship multiple
versions of things like this.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2024-12-11 16:40:04 | Re: Track the amount of time waiting due to cost_delay |
Previous Message | Andres Freund | 2024-12-11 16:34:07 | Re: FileFallocate misbehaving on XFS |