| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Siegfried Kiermayer <sicaine(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Segfault when running postgres inside kubernetes with huge pages |
| Date: | 2023-11-08 14:57:26 |
| Message-ID: | 667006.1699455446@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Siegfried Kiermayer <sicaine(at)gmail(dot)com> writes:
> we are using zalando postgres operator and i changed / set huge pages
> on kubernetes nodes from something undefined to 1536 (undefined
> because i was pretty sure before changing it to 1536 i saw an initial
> value of 1024 with 670 in use.
This previous discussion might hold the clue:
> I would go into more detail but honestly I believe this might be easy
> to find and I also assume it shouldn't segfault but return an error
> message indicating the / a issue.
There is not that much we can do about operating system bugs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Siegfried Kiermayer | 2023-11-08 15:03:53 | Re: Segfault when running postgres inside kubernetes with huge pages |
| Previous Message | hubert depesz lubaczewski | 2023-11-08 14:02:02 | Re: Logical replication is missing block of rows when sending initial sync? |