Re: [HACKERS] Revisiting NAMEDATALEN - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: [HACKERS] Revisiting NAMEDATALEN
Date
Msg-id 1AC89E24-0FBF-4477-9977-67E4026E2E22@gmail.com
Whole thread Raw
In response to Re: [HACKERS] Revisiting NAMEDATALEN  (Emrul <emrul@emrul.com>)
List pgsql-hackers
> On Jul 7, 2017, at 2:53 AM, Emrul <emrul@emrul.com> wrote:
>
> Tom, thank you for that pointer.  I get now that it is not free and therefore
> why its not something that should be changed by default.
>
> I guess the problem is 'build your own copy' (i.e. compiling from source) is
> something that sends most DB teams running into the hills.

To make matters worse, if you change NAMEDATALEN, compile, and run
'make check', some of the tests will fail.  The tests are very sensitive to the
exact output of the sql they execute, and changing NAMEDATALEN, or
indeed any one of many other options, causes some of the test output to
change. Even configure's options, such as --with-blocksize, cannot be
changed from the default value without potentially breaking the regression
tests.

mark


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] New partitioning - some feedback
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] pg_stop_backup(wait_for_archive := true) on standby server