Re: Revisiting NAMEDATALEN

From: Mark Dilger <hornschnorter(at)gmail(dot)com>
To: Emrul <emrul(at)emrul(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Revisiting NAMEDATALEN
Date: 2017-07-07 15:39:48
Message-ID: 1AC89E24-0FBF-4477-9977-67E4026E2E22@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> On Jul 7, 2017, at 2:53 AM, Emrul <emrul(at)emrul(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2017-07-07 15:50:04 Re: pg_stop_backup(wait_for_archive := true) on standby server
Previous Message Robert Haas 2017-07-07 15:39:19 Re: New partitioning - some feedback