Re: Improve logging when using Huge Pages
От | Justin Pryzby |
---|---|
Тема | Re: Improve logging when using Huge Pages |
Дата | |
Msg-id | ZJI51JzMSAyTkEjW@telsasoft.com обсуждение исходный текст |
Ответ на | Re: Improve logging when using Huge Pages (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: Improve logging when using Huge Pages
|
Список | pgsql-hackers |
On Tue, Jun 13, 2023 at 02:50:30PM +0900, Michael Paquier wrote: > On Mon, Jun 12, 2023 at 02:37:15PM -0700, Nathan Bossart wrote: > > Fair enough. I know I've been waffling in the GUC versus function > > discussion, but FWIW v7 of the patch looks reasonable to me. > > + Assert(strcmp("unknown", GetConfigOption("huge_pages_status", false, false)) != 0); > > Not sure that there is anything to gain with this assertion in > CreateSharedMemoryAndSemaphores(), because this is pretty much what > check_GUC_init() looks after? It seems like you misread the assertion, so I added a comment about it. Indeed, the assertion addresses the other question you asked later. That's what I already commented about, and the reason I found it compelling not to use a boolean. On Thu, Apr 06, 2023 at 04:57:58PM -0500, Justin Pryzby wrote: > I added an assert to check that a running server won't output > "unknown". On Wed, Jun 14, 2023 at 09:15:35AM +0900, Michael Paquier wrote: > There was a second thing that bugged me here. Would it be worth > adding some checks on huge_pages_status to make sure that it is never > reported as unknown when the server is up and running? -- Justin
Вложения
В списке pgsql-hackers по дате отправления: