| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: allow segment size to be set to < 1GiB |
| Date: | 2022-11-17 22:24:04 |
| Message-ID: | 714f98c1-7077-8ad7-364a-9570ba16c00f@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-11-17 Th 10:48, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> On 2022-11-17 09:58:48 -0500, Andrew Dunstan wrote:
>>> Are we going to impose some sane minimum, or leave it up to developers
>>> to discover that for themselves?
>> I don't think we should. It's actually useful to e.g. use 1 page sized
>> segments for testing, and with one exceptions the tests pass with it too. Do
>> you see a reason to impose one?
> Yeah, I think we should allow setting it to 1 block. This switch is
> only for testing purposes (I hope the docs make that clear).
>
>
Yeah clearly if 1 is useful there's no point in limiting it.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-11-17 22:26:52 | Re: Don't treate IndexStmt like AlterTable when DefineIndex is called from ProcessUtilitySlow. |
| Previous Message | Andrew Dunstan | 2022-11-17 22:11:00 | Re: Fix proposal for comparaison bugs in PostgreSQL::Version |