On Sat, Oct 28, 2023 at 04:04:47PM -0400, Bruce Momjian wrote:
> On Tue, Aug 2, 2022 at 08:08:07PM +, PG Doc comments form wrote:
> > 21.1.1 Loading or Reloading the Configuration
> > The pg_hba.conf file is read on start-up...
> > Note: The preceding statement...
> > The system view pg_
On Sat, Oct 28, 2023 at 03:14:32PM -0400, Bruce Momjian wrote:
> On Sat, Oct 28, 2023 at 02:42:06PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > Sorry, I attached a _colorized_ diff; here is a normal one.
> >
> > The new sentence is fine in isolation, but this doesn't feel like
> > a g
On Fri, Nov 3, 2023 at 05:04:46PM +, Daniel Westermann (DWE) wrote:
> >"Daniel Westermann (DWE)" writes:
> >>> Yeah, but populating it would not (unless many of the columns were
> >>> NULL).
>
> >> Ok, but then should the documentation be more precise? It seems a bit odd
> >> to
> let users
>"Daniel Westermann (DWE)" writes:
>>> Yeah, but populating it would not (unless many of the columns were
>>> NULL).
>> Ok, but then should the documentation be more precise? It seems a bit odd to
>> let users create such a table without at least a warning.
>Given the impact of NULLs, and the f
"Daniel Westermann (DWE)" writes:
>> Yeah, but populating it would not (unless many of the columns were
>> NULL).
> Ok, but then should the documentation be more precise? It seems a bit odd to
> let users create such a table without at least a warning.
Given the impact of NULLs, and the fact th
>"Daniel Westermann (DWE)" writes:
>> Creating a table with 1600 bigint columns does work with a 8k blocksize:
>Yeah, but populating it would not (unless many of the columns were
>NULL).
Ok, but then should the documentation be more precise? It seems a bit odd to
let users create such a table w
"Daniel Westermann (DWE)" writes:
> Creating a table with 1600 bigint columns does work with a 8k blocksize:
Yeah, but populating it would not (unless many of the columns were
NULL).
regards, tom lane
On Fri, Nov 3, 2023 at 5:09 PM Daniel Westermann (DWE)
wrote:
>
> Hi,
>
> from the limits page in the docs:
> https://www.postgresql.org/docs/current/limits.html
>
> "...but a tuple of 1600 bigint columns would consume 12800 bytes and would
> therefore not fit inside a heap page".
>
> Creating a
Hi,
from the limits page in the docs:
https://www.postgresql.org/docs/current/limits.html
"...but a tuple of 1600 bigint columns would consume 12800 bytes and would
therefore not fit inside a heap page".
Creating a table with 1600 bigint columns does work with a 8k blocksize:
$ cat gen_tab.sh
On Fri, 2023-11-03 at 09:53 -0400, Bruce Momjian wrote:
> On Thu, Nov 2, 2023 at 09:51:58PM -0400, Bruce Momjian wrote:
> > On Wed, Nov 1, 2023 at 09:31:52PM +0100, Laurenz Albe wrote:
> > > There is another patch in the current commitfest that addresses a similar
> > > problem, triggered by anot
On Thu, Nov 2, 2023 at 09:51:58PM -0400, Bruce Momjian wrote:
> On Wed, Nov 1, 2023 at 09:31:52PM +0100, Laurenz Albe wrote:
> > There is another patch in the current commitfest that addresses a similar
> > problem, triggered by another complaint:
> > https://commitfest.postgresql.org/45/4633/
>
11 matches
Mail list logo
