| From: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> |
|---|---|
| To: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: llvm dependency and space concerns |
| Date: | 2025-01-11 23:33:35 |
| Message-ID: | Z4L_z9QAzhV7Pw0l@elch.exwg.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
## Jeremy Schneider (schneider(at)ardentperf(dot)com):
> I'm running Postgres in containers, and recently did some analysis of
> the total container sizes. I posted some analysis over on the debian
> packaging mailing list [1] [2]. The TLDR is that LLVM alone makes up
> 33% of a postgres container's bytes (143MB / 434MB) [1].
Does that even matter compared with the size of the database itself?
> I haven't yet looked closely, but my assumption is that the --with-llvm
> flag may not work the same. I'm going to spend some time taking a look,
> but if someone knows off the top of their head and can give me a head
> start that would be appreciated!
Have a look at the RPM packages and how they split off postgresql-llvmjit
there:
https://git.postgresql.org/gitweb/?p=pgrpms.git;a=tree;f=rpm/redhat/main/non-common/postgresql-17/main;hb=HEAD
Regards,
Christoph
--
Spare Space
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2025-01-11 23:49:08 | Re: Adjusting hash join memory limit to handle batch explosion |
| Previous Message | Paul Jungwirth | 2025-01-11 23:19:26 | Re: SQL:2011 application time |