> Hello PostgreSQL Community,
>
> I am writing to propose an alternative compilation of PostgreSQL that
> allows for a 256-byte identifier length limit, alongside the existing
> 64-byte version.
>
> *Problem:*
> The current limit of 63 bytes can be quite restrictive, especially for
> databases th
On Tue, Oct 10, 2023 at 08:22:55AM +0200, Laurenz Albe wrote:
> On Tue, 2023-10-10 at 11:49 +0800, David HJ wrote:
> > I am writing to propose an alternative compilation of PostgreSQL that allows
> > for a 256-byte identifier length limit, alongside the existing 64-byte
> > version.
> >
> > Proble
On Tue, 2023-10-10 at 11:49 +0800, David HJ wrote:
> I am writing to propose an alternative compilation of PostgreSQL that allows
> for a 256-byte identifier length limit, alongside the existing 64-byte
> version.
>
> Problem:
> The current limit of 63 bytes can be quite restrictive, especially f
Hello PostgreSQL Community,
I am writing to propose an alternative compilation of PostgreSQL that
allows for a 256-byte identifier length limit, alongside the existing
64-byte version.
*Problem:*
The current limit of 63 bytes can be quite restrictive, especially for
databases that use multi-byte
Hi All,
Maybe somebody could help come up with an idea on how to resolve this.
The situation is as follows:
1. We have a huge (10 billion rows) table with customer operations
2. It needs to be searched by several criteria at the same time - one of them
is text similarity (and we decided to try
Tyvvm, will try
Best Regards,
Anuwat Sagulmontreechai (Max)
Soft Square Group of Companies
Tel. 02-997-2000 ext.2305
-Original Message-
From: Laurenz Albe
Sent: Friday, October 6, 2023 2:43 AM
To: Anuwat Sagulmontreechai ;
pgsql-general@lists.postgresql.org
Cc: jakari...@softsquaregro
On Thu, Oct 5, 2023 at 4:25 PM Lauri Kajan wrote:
> In my dreams the plan would be something like this:
> Nested Loop
> -> Index Scan using dealers_pkey on dealers
> Index Cond: (id = ANY ('{54,12,456,315,468}'::integer[]))
> -> Append
> -> Bitmap Heap Scan on bikes
>
