RE: pgcon unconference / impact of block size on performance

From: Jakub Wartak <Jakub(dot)Wartak(at)tomtom(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: RE: pgcon unconference / impact of block size on performance
Date: 2022-06-07 09:46:53
Message-ID: PR3PR07MB82434ED323B18CFA6AF7C834F6A59@PR3PR07MB8243.eurprd07.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[..]
>I doubt we could ever
> make the default smaller than it is today as it would nobody would be able to
> insert rows larger than 4 kilobytes into a table anymore.

Add error "values larger than 1/3 of a buffer page cannot be indexed" to that list...

-J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thibaud W. 2022-06-07 09:49:21 Re: Proposal: adding a better description in psql command about large objects
Previous Message Jakub Wartak 2022-06-07 09:46:51 RE: pgcon unconference / impact of block size on performance