From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
Cc: | Денис Романенко <deromanenko(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: NAMEDATALEN increase because of non-latin languages |
Date: | 2021-08-18 11:33:34 |
Message-ID: | CAOBaU_bdz8qMpK05BXZ9jbLXkasds3Kyes3AO0aUqpp--O8B1A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Aug 18, 2021 at 7:27 PM John Naylor
<john(dot)naylor(at)enterprisedb(dot)com> wrote:
>
> On Wed, Aug 18, 2021 at 7:15 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> >
> > Unfortunately, the problem isn't really the additional disk space it
> > would require. The problem is the additional performance hit and
> > memory overhead, as the catalog names are part of the internal
> > syscache.
>
> Some actual numbers on recent hardware would show what kind of tradeoff is involved. No one has done that for a long time that I recall.
Agreed, but I don't have access to such hardware. However this won't
influence the memory overhead part, and there is already frequent
problems with that, especially since declarative partitioning, so I
don't see how we could afford that without some kind of cache TTL or
similar. AFAIR the last discussion about it a few years ago didn't
lead anywhere :(
From | Date | Subject | |
---|---|---|---|
Next Message | Денис Романенко | 2021-08-18 11:43:18 | Re: NAMEDATALEN increase because of non-latin languages |
Previous Message | John Naylor | 2021-08-18 11:27:42 | Re: NAMEDATALEN increase because of non-latin languages |