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

From Emrul
Subject Re: [HACKERS] Revisiting NAMEDATALEN
Date
Msg-id 1499421187021-5970351.post@n3.nabble.com
Whole thread Raw
In response to Re: [HACKERS] Revisiting NAMEDATALEN  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Revisiting NAMEDATALEN
Re: [HACKERS] Revisiting NAMEDATALEN
List 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.



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [HACKERS] Oddity in error handling of constraint violation inExecConstraints for partitioned tables
Next
From: Michael Meskes
Date:
Subject: Re: [HACKERS] Rust bindings to pgtypes lib