pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedbtree index maximum row size
3+ messages / 3 participants
[nested] [flat]
* btree index maximum row size
@ 2020-02-03 19:09 PG Doc comments form <noreply@postgresql.org>
2020-03-13 00:17 ` Re: btree index maximum row size Bruce Momjian <bruce@momjian.us>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2020-02-03 19:09 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: davidmaxwell@gmail.com
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/limits.html
Description:
Appendix K (PostgreSQL Limits) - doesn't mention the (btree) index row size
limits. I think that it should.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: btree index maximum row size
2020-02-03 19:09 btree index maximum row size PG Doc comments form <noreply@postgresql.org>
@ 2020-03-13 00:17 ` Bruce Momjian <bruce@momjian.us>
2020-03-13 00:56 ` Re: btree index maximum row size Peter Geoghegan <pg@bowt.ie>
0 siblings, 1 reply; 3+ messages in thread
From: Bruce Momjian @ 2020-03-13 00:17 UTC (permalink / raw)
To: davidmaxwell@gmail.com; pgsql-docs@lists.postgresql.org
On Mon, Feb 3, 2020 at 07:09:19PM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/limits.html
> Description:
>
> Appendix K (PostgreSQL Limits) - doesn't mention the (btree) index row size
> limits. I think that it should.
Sorry for the delay in replying. We do get questions about the btree
length limit occasionally, but practically the length limit usually
isn't a problem. Unless you need ordered data, a hash index is a better
choice for long values than btree because the hashes are much shorter.
Expression indexes can also help.
What is your use-case for indexing very long values?
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: btree index maximum row size
2020-02-03 19:09 btree index maximum row size PG Doc comments form <noreply@postgresql.org>
2020-03-13 00:17 ` Re: btree index maximum row size Bruce Momjian <bruce@momjian.us>
@ 2020-03-13 00:56 ` Peter Geoghegan <pg@bowt.ie>
0 siblings, 0 replies; 3+ messages in thread
From: Peter Geoghegan @ 2020-03-13 00:56 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: davidmaxwell@gmail.com, Pg Docs <pgsql-docs@lists.postgresql.org>
On Thu, Mar 12, 2020 at 5:17 PM Bruce Momjian <bruce@momjian.us> wrote:
> Sorry for the delay in replying. We do get questions about the btree
> length limit occasionally, but practically the length limit usually
> isn't a problem.
Technically the limitation is documented elsewhere, since it is a
limitation of the B-Tree access method specifically. However, I think
that there is a good practical argument to be made for including it
here as well.
--
Peter Geoghegan
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2020-03-13 00:56 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-02-03 19:09 btree index maximum row size PG Doc comments form <noreply@postgresql.org>
2020-03-13 00:17 ` Bruce Momjian <bruce@momjian.us>
2020-03-13 00:56 ` Peter Geoghegan <pg@bowt.ie>
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