From: Sebastien Flaesch <sebastien.flaesch@4js.com>
To: Christophe Pettus <xof@thebuild.com>
CC: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: pgvector as standard PostgreSQL feature?
Thread-Topic: pgvector as standard PostgreSQL feature?
Thread-Index: AQHbmJn2JKCBHmEf4UyFr5e5BEFOa7N6HgYAgAAEiMw=
Date: Wed, 19 Mar 2025 08:39:54 +0000
Message-ID:
 <DBAP191MB1289045AB4FC35F7039D0542B0D92@DBAP191MB1289.EURP191.PROD.OUTLOOK.COM>
References:
 <DBAP191MB12893E8288EBE762637FA86CB0D92@DBAP191MB1289.EURP191.PROD.OUTLOOK.COM>
 <558AE558-C724-435B-9F32-F40966A20907@thebuild.com>
In-Reply-To: <558AE558-C724-435B-9F32-F40966A20907@thebuild.com>
Accept-Language: en-US
Content-Language: en-US
msip_labels:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: DBAP191MB1289:EE_|AS4P191MB2040:EE_
x-ms-office365-filtering-correlation-id: 12425750-d0db-4afc-6c32-08dd66c19f2a
x-volarisppoutbound: true
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam:
 BCL:0;ARA:13230040|1800799024|366016|376014|38070700018|8096899003|7053199007;
x-microsoft-antispam-message-info:
 =?us-ascii?Q?yxuw+Qy9ySRzUnHekz0PHH5GCiEGRXg+yxJYl0ZxcUHakQ7zFvvlRm1PCvCm?=
 =?us-ascii?Q?OYBET7qh3HyB5rPPOzSExPHFj0I83+1JoeND+QUxrgWANzbOmNeg5t6Pf1QC?=
 =?us-ascii?Q?1PojyH8WO5voG/jChex0TPmiE0HcrmRY8f8clSmjzDZA3trEmfS8OJCkZK3i?=
 =?us-ascii?Q?hDEPJZacF+38OSJnSnVl3SfHq7j6Dh32WHOz6CZVTU+ku8BEColB5R2S1ewt?=
 =?us-ascii?Q?ip1mQwXkPGfupMLGYdIIJu20o92Fuo8ju22IG6XoI3bKYmvQ8WlR/PacR7Gv?=
 =?us-ascii?Q?V/elU6fm1YPVtHrc7G88f8Axt2XA9mi0gCBy8vasAZqsNg08e9grDbxCVoGf?=
 =?us-ascii?Q?YPhibvIVWt5Ee3lFP7U4Ac5IC/VxbC/nR0SnGxueU53ibmE+Qjf+/gxX59uo?=
 =?us-ascii?Q?vrtyEFKaDCjhT3CsKL79a7HQ1ENov0onu2ZulgzDDeCQOFpdv1H7XpqHxWMw?=
 =?us-ascii?Q?QZ4YfsXThuPKqnCAnOFuDh34fr1lidJNBpUp7K7FEq4xgkB/RCGFt+o9vIAF?=
 =?us-ascii?Q?vF7GG9sFD5awKg9bfW993CqXqzRIWhEYqfLmpRqZjK9INmP7hji+M0B/2iQ8?=
 =?us-ascii?Q?DMGFox7Y6rtLyfQDiymI6OMO4dYCrxUrCl/nw7X7NxuQRPkMUaT+1wlMsMnc?=
 =?us-ascii?Q?SQPmMQuFQKm3qvsb/35+m7vUEGyI5uDTdm/EkTOd2uJCaOMowW2kwP2DWkx7?=
 =?us-ascii?Q?8jhitiC2bncA/3T7TOgaV6wYbPo/vV1MmSnSdjMGUInn1z4CCP/WjyF0SP9d?=
 =?us-ascii?Q?JExUxl+yQcZN2L+rhuJWDQcD4TAR0VMyTj6mq8QZr1ubJ8Hj5WRwZbO7g/N/?=
 =?us-ascii?Q?VeJIV2lmo6ZYc6qeUX4/WPDeAiD0JmFVZpzAGFHS0Qi2NHDIa5BVTxy+PPEt?=
 =?us-ascii?Q?hsRR00aem/NIY4A1TMnilsYwbltFT4ezwSBr3x1HoFxmVfJPa1pMFraMoIX7?=
 =?us-ascii?Q?n+xZW62qsbEu2BSjJVZZqu8nuhKxIqy7/iUwIiVdIaZ+WwSA9G8On6sKG8XP?=
 =?us-ascii?Q?fXC5uOmz/kprxLs52x04OHrhzZytH3eG1k8QCQ34ILImyaLLpqwa+0X+iY0s?=
 =?us-ascii?Q?iI+hrhzCQ7C1qsrSLHvjVZhqzhRuae2Mz/Bg7ALZEA6b0TOvv3jJ/vT3xiZJ?=
 =?us-ascii?Q?I1IC5riWJ+Ovdq8XOMhGXLHcyoTPhOFiVttyvESJtdd8EjIL3iH2gPSGofrS?=
 =?us-ascii?Q?sCysI9Uvb069dgknAyTctCizzg5e5AzPVYNpPwmRANmxT6UUV8ZoUmBGsQ1C?=
 =?us-ascii?Q?P3HSiRmAoHuXKIz+P+/naexF+O2L7byTEgji/toXWPTZnCxovxML7AqPzSAm?=
 =?us-ascii?Q?I3X8P5XOEdI4KdDzPI7/NWAh+5W8w3RwLTMjWCkMGdnN5MkcmkN1qJiWRP5q?=
 =?us-ascii?Q?T8tIMxDopDsShs0W6hDZvo8cXgZJa4s0KrDQ7eOuFAQkpWk+Y7iQEZ2WUtTp?=
 =?us-ascii?Q?thNAdBxOvkgGpGpYdw0X/1UtygFbYEfo?=
x-forefront-antispam-report:
 CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DBAP191MB1289.EURP191.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230040)(1800799024)(366016)(376014)(38070700018)(8096899003)(7053199007);DIR:OUT;SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0:
 =?us-ascii?Q?9IMMhvTIGWdYW1n1/xS8PypCuzagh8XwMQ9JRUXsL9x4Gv1MjZIiLQgYAQbK?=
 =?us-ascii?Q?3lG5fomFnHubzVc6EnDnMOuy5mjYq58bpQfT0KIgo0O8Q13QZ1z1mtQ1sHgx?=
 =?us-ascii?Q?+jkxK0n1tRnEoOAVti5ykSbHP9yrNdSL+MaY9BqVnmNem3NdO/bRRJRZla5w?=
 =?us-ascii?Q?9mZca98ACJA4FLY7khWjmyBXT7fihtf0FwOdIWqtf0F0+K0pSnVRD8eoPUUc?=
 =?us-ascii?Q?hbiEzQa4Vr2zVQGiwo5pKcDvnmsSBTlWmppUXCu40LfwQHhY2lPjk2ZuaLPf?=
 =?us-ascii?Q?9/H/O0IP/xYXc6+azBjKMI3TRmvasf4XmB+Jo1xUZ1xIr+ziMWixl4KPez6x?=
 =?us-ascii?Q?ZyzL0Ay4c9kNUnjYOqrEH1Ng0H7oRp/TTcCAT+ZcguTt1If4Srmd1rXV76Pk?=
 =?us-ascii?Q?RDyy4Cbts7+/hwyKiiOqdUYXes5XkYDyhLFkc5sdVfXK3l/1VWWWd029y2HR?=
 =?us-ascii?Q?K+L4t9Rb2AD2v9WP4tTvbtIbJHr78t1MQzim+CQKxQFGH7KBfxditpGIOw4d?=
 =?us-ascii?Q?TOOxdZOi+1v9/3LwE9mf6hugCQPnhxGupFfeALcuc/AUluHcdWJdr2YmAXXN?=
 =?us-ascii?Q?NqxsCoQ80LG0WjwFLxBfMbDFH1fYOthMHZjx2fdChggnABcG7/WBakMKQCHQ?=
 =?us-ascii?Q?a6xDpCrwUSzUiV0X2huY23lC+7r1Gli7gpfBD24hC5yHv24Skz4dZUbxKAhJ?=
 =?us-ascii?Q?hBWUxyVIBmP657rOYEpFp2SBlHHNcO+qz/2sXde5WEIYE5y1tBCUgucIbPMI?=
 =?us-ascii?Q?pRfPYXENQtgqqmoWosuxWt5950IW32fXdGieB6UH93sqP3e/VnxhlDBZmMO/?=
 =?us-ascii?Q?I3CJCD2zRfmObT3VNOwmqYTmQUPi0KKIufLO9JkzPNqfTDHPD0bXQtQu/Oc5?=
 =?us-ascii?Q?TRbDVSbZJ0m4anAzTeNKLGDXaz04c4Li6s3SaEd1iZ1L1Df8EodecfZo16oR?=
 =?us-ascii?Q?k0AEzcWXeQk15UOwuvG3rxWd1FQuwlRA9QpwwIrLH/Z5Aw82rnIAHZH9xS16?=
 =?us-ascii?Q?qF8ZYR2/r95ikWRsHp1/5GZBcO8gsTAvAJSJMzfri327cFxcCv1hNwGU2Vg4?=
 =?us-ascii?Q?rhlCjCEwg3t+v+fijykHz4WVTmCpeJkB8b+74YQ+tCSH9vlKfHkZYaI9Ndcj?=
 =?us-ascii?Q?i60YChU6tAn/NP/vLj2PI1TYGO6pxLuEIaJ+TLM+v9tW5vb7DcTu+f9SH5BV?=
 =?us-ascii?Q?wwvs73vh+m2QkjGRnGipq/Wxn9Fb+mQOjEdbkOw1477wMKEPWcyWLiW410ZG?=
 =?us-ascii?Q?ZmnFSE4lL9q6BUppgp8Ij9O/NiVIINF2l++9vAeLiuHpOx2Jved6zfLtVJ9x?=
 =?us-ascii?Q?hKz9FNlTfmKJ39nXIFgde+7vUaLsLGeJIOyt/9vwqgWNwfe2w/qXDWghEBkQ?=
 =?us-ascii?Q?m2xf5972xl0ubOtK1zlXVWsxuCjFDnm3UpaY23ZX1xRh09I3mNXw0pmqlu7L?=
 =?us-ascii?Q?c/MIoGxiPBR2m55mJ+gYBMKnNubDxUiCQyeoMwKJEA8FKnD1FHrcOSOmFzwS?=
 =?us-ascii?Q?2HRnRXHiiaRvWtfPni/uSzIRxMIIZDXLgrxxrPnw+ilCs4u6Vh/v7ny63DkU?=
 =?us-ascii?Q?MVSj2rjAFZQ5ni28S1NOPA4eFxhOir1SxNDKwHK4?=
Content-Type: multipart/alternative;
	boundary="_000_DBAP191MB1289045AB4FC35F7039D0542B0D92DBAP191MB1289EURP_"
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-ExternalHop-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-ExternalHop-MessageData-0:
	OCeOQsOODRLu7/j0V/xYddplT2lnbnHpkXAaSP8SN9G+m8cZBhgmD3o6PHtmv+zqk6bHEXfz9eueFnXsxNbt0RKEr9n+/vFhqy0Q5VL5Ja0nG/sbYIQV/G3Yg5eKjCR40UXLZJJAkEs3VJnGj4zYfnCzy9TiTCOONp10y4eZOZ6UUG3nsZHDLdbL9roa05cPPyAAXweqSW9YyLDE2bdWXflgiZlNdHAin5zDdcqQ9RmagJVQ6JqrKEYAOEL2fv2D1pRQmSGfXC9Qzbml4smZ+oc2GtKGbYOYU3iteW+4oXhBV6oYfnNZg/0scIzKQ2wlUEUZpkeZJ+eKdmMLXixgHzgLOr7DO0evGrgKRtea+Ii7f7ekd/n7WQxI0u6weDohMOkCOpV37RuSrfEqSu997TavknGDQKjRymzwm9zgyLbMiPaJl7Ai6ICHXgWheKBNQzT5+izcCIDUxKw/qyBabmI1tQjxUVF52M6FVnV1cqx/ycBRmmP1/3ShFGErffDqF69/OqD+NGi3lw+6HxFDWE/NCvKlswfLeLgI7yXUyxBf/UB6VVXaohHOfBeeJ1v/w5Ruza+IG0aUTgfPoONTXmflKTGMx+TIT44ySfu6GsmT6lMUg+f8st6GtZArmcSs6GAtRMiYhj7fBRzeCtolxw==
X-OriginatorOrg: 4js.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DBAP191MB1289.EURP191.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 12425750-d0db-4afc-6c32-08dd66c19f2a
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2025 08:39:54.1437
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 75c696ec-5bfb-4892-9a0c-9187a9061cd6
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: y46rNbAQ28nDLTTsCkmR7HBW1O/fzQaCV2xfcUAi+5/YOnw478Ksk6DnlHOlaY8KrzdcceKlFCAPRyI2eJRQrpg0a6aaMNVcr5eBQsSo/ys=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AS4P191MB2040
X-Authority-Analysis: v=2.4 cv=SqOQ6OO0 c=1 sm=1 tr=0 ts=67da82dd cx=c_pps a=Qf1mswPHpNN1WXcnD2EiMQ==:117 a=lCpzRmAYbLLaTzLvsPZ7Mbvzbb8=:19 a=wKuvFiaSGQ0qltdbU6+NXLB8nM8=:19 a=Ol13hO9ccFRV9qXi2t6ftBPywas=:19 a=xqWC_Br6kY4A:10 a=Vs1iUdzkB0EA:10
 a=H5OGdu5hBBwA:10 a=udrfY5dcTTYA:10 a=wf_yTYXYAAAA:8 a=YiSXs9CjAAAA:8 a=epTmVMiNAAAA:8 a=UQYS_iiZRSXW5EBZaGwA:9 a=CjuIK1q_8ugA:10 a=ot77EqbbxsNFh4qC5AMA:9 a=Zya5y-88t6XGlAP_:21 a=frz4AuCg-hUA:10 a=_W_S_7VecoQA:10 a=hSGMlWDd2ZYrfeZIb8_S:22
 a=i3Kcs0zRCnBKJ3xysGeB:22
X-Proofpoint-ORIG-GUID: 4MEcBZg0y9geTvkmLNJiJ2cABg1T_Y2z
X-Proofpoint-GUID: 4MEcBZg0y9geTvkmLNJiJ2cABg1T_Y2z
X-ProofpointHeader: Yes
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 clxscore=1011
 mlxlogscore=816 bulkscore=0 adultscore=0 suspectscore=0 lowpriorityscore=0
 priorityscore=1501 phishscore=0 malwarescore=0 mlxscore=0 spamscore=0
 classifier=spam authscore=0 authtc=n/a authcc= route=outbound adjust=0
 reason=mlx scancount=1 engine=8.21.0-2502280000
 definitions=main-2503190058
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/DBAP191MB1289045AB4FC35F7039D0542B0D92%40DBAP191MB1289.EURP191.PROD.OUTLOOK.COM>
Precedence: bulk

--_000_DBAP191MB1289045AB4FC35F7039D0542B0D92DBAP191MB1289EURP_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Go it, makes total sense.

So pgvector etc will probably remain an extension for a while.

Thanks for the note about BIT type.
I have missed that it's a standard built-in type.

Seb
________________________________
From: Christophe Pettus <xof@thebuild.com>
Sent: Wednesday, March 19, 2025 9:19 AM
To: Sebastien Flaesch <sebastien.flaesch@4js.com>
Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: Re: pgvector as standard PostgreSQL feature?

EXTERNAL: Do not click links or open attachments if you do not recognize th=
e sender.

> On Mar 19, 2025, at 07:47, Sebastien Flaesch <sebastien.flaesch@4js.com> =
wrote:
>
> Is there a plan to get pgvector's types (vector, halfvec, sparsevec, bit)=
 implemented as native built-in data types like json/jsonb ?

(I'm speaking just for myself here.)  I would not base any plans on this fu=
nctionality being available in the PostgreSQL core in the near future (and =
by "near future," I mean the next five years).

1. You list three different extensions with overlapping functionality, and =
that's a good sign that there isn't consensus on what the features that wou=
ld be offered in core should be.

2. Adding a type to the core distribution (or even to contrib/) creates a m=
aintenance burden on the core developers, and that's not something assumed =
lightly.  Once a type is in core, it (almost) never can be removed, and the=
 more specialized the type and detailed the implementation, the greater the=
 risk that the developers who know and care about it won't be available in =
the future.  Search the archives for a discussion of the "money" type for w=
hat happens when a type added to core starts becoming ill-supported... and =
"money" isn't anywhere near as complex as vector functionality.

3. PostgreSQL is designed to have a rich ecosystem of extensions.  The abil=
ity to add this kind of functionality in an extension is exactly what disti=
nguishes PostgreSQL from many other RDBMS systems.  There's no burning need=
 to add functionality like this to core.

It is true that hosted environments take time to adopt new extensions (alth=
ough AWS RDS has supported pgvector for nearly two years now), but that's n=
ot in itself a reason to move things into core.

> Side note: I have some doubts about these type names, especially "bit" ..=
. why not "bitvec"?

BIT and BIT VARYING are the SQL standard names for these types.


--_000_DBAP191MB1289045AB4FC35F7039D0542B0D92DBAP191MB1289EURP_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
Go it, makes total sense.</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
So pgvector etc will probably remain an extension for a while.</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
Thanks for the note about BIT type.</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
I have missed that it's a standard built-in type.</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
Seb</div>
<div id=3D"appendonsend"></div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Christophe Pettus &lt=
;xof@thebuild.com&gt;<br>
<b>Sent:</b> Wednesday, March 19, 2025 9:19 AM<br>
<b>To:</b> Sebastien Flaesch &lt;sebastien.flaesch@4js.com&gt;<br>
<b>Cc:</b> pgsql-general@postgresql.org &lt;pgsql-general@postgresql.org&gt=
;<br>
<b>Subject:</b> Re: pgvector as standard PostgreSQL feature?</font>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;=
">
<div class=3D"PlainText">EXTERNAL: Do not click links or open attachments i=
f you do not recognize the sender.<br>
<br>
&gt; On Mar 19, 2025, at 07:47, Sebastien Flaesch &lt;sebastien.flaesch@4js=
.com&gt; wrote:<br>
&gt;<br>
&gt; Is there a plan to get pgvector's types (vector, halfvec, sparsevec, b=
it) implemented as native built-in data types like json/jsonb ?<br>
<br>
(I'm speaking just for myself here.)&nbsp; I would not base any plans on th=
is functionality being available in the PostgreSQL core in the near future =
(and by &quot;near future,&quot; I mean the next five years).<br>
<br>
1. You list three different extensions with overlapping functionality, and =
that's a good sign that there isn't consensus on what the features that wou=
ld be offered in core should be.<br>
<br>
2. Adding a type to the core distribution (or even to contrib/) creates a m=
aintenance burden on the core developers, and that's not something assumed =
lightly.&nbsp; Once a type is in core, it (almost) never can be removed, an=
d the more specialized the type and detailed
 the implementation, the greater the risk that the developers who know and =
care about it won't be available in the future.&nbsp; Search the archives f=
or a discussion of the &quot;money&quot; type for what happens when a type =
added to core starts becoming ill-supported...
 and &quot;money&quot; isn't anywhere near as complex as vector functionali=
ty.<br>
<br>
3. PostgreSQL is designed to have a rich ecosystem of extensions.&nbsp; The=
 ability to add this kind of functionality in an extension is exactly what =
distinguishes PostgreSQL from many other RDBMS systems.&nbsp; There's no bu=
rning need to add functionality like this
 to core.<br>
<br>
It is true that hosted environments take time to adopt new extensions (alth=
ough AWS RDS has supported pgvector for nearly two years now), but that's n=
ot in itself a reason to move things into core.<br>
<br>
&gt; Side note: I have some doubts about these type names, especially &quot=
;bit&quot; ... why not &quot;bitvec&quot;?<br>
<br>
BIT and BIT VARYING are the SQL standard names for these types.<br>
<br>
<br>
<br>
</div>
</span></font></div>
</body>
</html>

--_000_DBAP191MB1289045AB4FC35F7039D0542B0D92DBAP191MB1289EURP_--