| From: | Ba Jinsheng <bajinsheng(at)u(dot)nus(dot)edu> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Performance of Query 4 on TPC-DS Benchmark |
| Date: | 2024-11-11 10:51:16 |
| Message-ID: | SEZPR06MB649467407B292F9979DFD6788A582@SEZPR06MB6494.apcprd06.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>> The default configurations of PostgreSQL incur the error: "ERROR: could not resize shared memory segment "/PostgreSQL.3539600020" to 2097152 bytes: No space left on device"
>No comment on your optimiser experiments for now, but for this error:
>it reminds me of a low/default --shm-size limit from Docker, or other
>similar container stuff?
Aha, you are right. The error disappears if running PostgreSQL out of docker container.
Notice: This email is generated from the account of an NUS alumnus. Contents, views, and opinions therein are solely those of the sender.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios - cloud | 2024-11-12 10:37:27 | Re: tds_fdw : Severe performance degradation from postgresql 10.23 to 16.4 |
| Previous Message | Ba Jinsheng | 2024-11-11 10:49:56 | Re: Performance of Query 4 on TPC-DS Benchmark |