pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vitale, Anthony, Sony Music <anthony.vitale@sonymusic.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: ERROR: index row size 2720 exceeds btree version 4 maximum 2704 for index in V14 but pg_column_size calculates 2701
Date: Wed, 24 Apr 2024 12:57:03 -0400
Message-ID: <3722468.1713977823@sss.pgh.pa.us> (raw)
In-Reply-To: <AS8PR02MB10078358D14082084A46AC94299102@AS8PR02MB10078.eurprd02.prod.outlook.com>
References: <AS8PR02MB10078358D14082084A46AC94299102@AS8PR02MB10078.eurprd02.prod.outlook.com>

"Vitale, Anthony, Sony Music" <anthony.vitale@sonymusic.com> writes:
> I am trying to figure out how to calculate a column size in my UTF8 encoded Postgresql V14 instance in order to avoid the error exceeds btree version 4 maximum 2704  and I am obviously not doing it correctly using pg_column_size as when I do I get 2701 which is lower than 2704.

I think you're not accounting for overhead.  The reported index row
size would include the index tuple header (8 bytes) as well as
alignment padding.

			regards, tom lane





view thread (2+ messages)

Message-ID: <3722468.1713977823@sss.pgh.pa.us>
Permalink:  ../3722468.1713977823@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3722468.1713977823@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, anthony.vitale@sonymusic.com, pgsql-admin@lists.postgresql.org
  Subject: Re: ERROR: index row size 2720 exceeds btree version 4 maximum 2704 for index in V14 but pg_column_size calculates 2701
  In-Reply-To: <3722468.1713977823@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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