Re: Large files for relations - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Large files for relations
Date
Msg-id CA+Tgmob_QjHfZbkoizF=aH4kXH9ih=E2uffvRpBUfNe6D_LGXw@mail.gmail.com
Whole thread Raw
In response to Re: Large files for relations  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On Wed, May 24, 2023 at 2:18 AM Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
> > What I'm hearing is that something simple like this might be more acceptable:
> >
> > * initdb --rel-segsize (cf --wal-segsize), default unchanged
>
> makes sense

+1.

> > * pg_upgrade would convert if source and target don't match
>
> This would be good, but it could also be an optional or later feature.

+1. I think that would be nice to have, but not absolutely required.

IMHO it's best not to overcomplicate these projects. Not everything
needs to be part of the initial commit. If the initial commit happens
2 months from now and then stuff like this gets added over the next 8,
that's strictly better than trying to land the whole patch set next
March.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Atomic ops for unlogged LSN
Next
From: Tomas Vondra
Date:
Subject: Re: memory leak in trigger handling (since PG12)