Re: Revisiting NAMEDATALEN

From: Emrul <emrul(at)emrul(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Revisiting NAMEDATALEN
Date: 2017-07-07 09:53:07
Message-ID: 1499421187021-5970351.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

A solution might be to make NAMEDATALEN configurable without having to
recompile source (perhaps a config variable or an initdb parameter). When I
have some free time I will investigate whether this is doable.

--
View this message in context: http://www.postgresql-archive.org/Revisiting-NAMEDATALEN-tp5969858p5970351.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2017-07-07 10:54:33 Re: Rust bindings to pgtypes lib
Previous Message Amit Langote 2017-07-07 09:47:26 Re: Oddity in error handling of constraint violation in ExecConstraints for partitioned tables