Re: initdb / bootstrap design
От | Tom Lane |
---|---|
Тема | Re: initdb / bootstrap design |
Дата | |
Msg-id | 3404857.1645044123@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: initdb / bootstrap design (Andres Freund <andres@anarazel.de>) |
Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> writes: > On 2022-02-16 13:24:41 -0500, Tom Lane wrote: >> I remembered the reason why it's done that way: if we replaced those >> values during genbki.pl, the contents of postgres.bki would become >> architecture-dependent, belying its distribution as a "share" file. > Hm. Architecturally I still would like to move it to be processed server > side. I'd like to eventually get rid of single user mode (but keep bootstrap, > at least for longer). > Seems we could make NAMEDATALEN, FLOAT8PASSBYVAL, ALIGNOF_POINTER, > FLOAT8PASSBYVAL stuff that bootparse knows about? And remove the need for > POSTGRES, ENCODING, LC_COLLATE, LC_CTYPE as discussed already? Yeah, I have no objection to doing it that way. It should be possible to do those substitutions on a per-field basis, which'd be cleaner than what initdb does now ... regards, tom lane
В списке pgsql-hackers по дате отправления: