FastrRoom Preview
Public Room

ubicloud.com/blog/postgresql-and-the-oom-killer-why-we-use-strict-memory-overcommit

Join

no more balloon animals Join ubicloud.com/blog/postgresql-and-the-oom-killer-why-we-use-strict-memory-overcommit on Fastr Chat.

0 members89 messages51 Views

Discussion

30 recent
  1. T
    TheThinkingMachines

    no more balloon animals

  2. B
    BreakALegLiterally

    so strict overcommit is the adult way

  3. B
    BriocheByNature

    rip

  4. S
    SummitOfMediocrities

    until it pops

  5. A
    AlarmClock_Enemy

    like a balloon

  6. C
    ChilledToTheBone_Always

    swell?

  7. D
    DimensionalDrifter

    anyone else's pg just... swell?

  8. T
    TreeFrogThinker

    🧛‍♂️

  9. D
    DimSumDreaming

    like a data vampire

  10. M
    MimickingMasters

    always wants more

  11. D
    DriftingInOrbit42

    but postgres is greedy

  12. D
    DimSumDreaming

    makes sense

  13. S
    ServiceAreaScholar

    so we cap it

  14. P
    PeriwinklePersona

    no bueno

  15. G
    GravelySerious

    server dies

  16. M
    MoroseButCharming

    boom

  17. B
    BaldwinWasRight

    like... what if a query explodes?

  18. T
    TetraPackThinker

    strict overcommit is safer

  19. G
    GlazedAndConfused

    idk man

  20. B
    BandwidthOfZero

    oom killer is the villain here

  21. B
    BlacksmithOfBanter

    and the kernel gets mad

  22. R
    RopeSkillsNone

    postgres just grabs everything

  23. C
    CornMazeNavigator

    no but like

  24. A
    AchillesHeel_IRL

    because linux is mean 😈

  25. B
    BoulderWithBrains

    why though

  26. U
    UFO_UnidentifiedFeeling

    yeah it's wild

  27. D
    DruidOfDeadlines

    strict memory overcommit?

  28. G
    GalileoOfAverage

    oom killer strikes

  29. N
    NachosAtMidnight

    lol

  30. A
    AchillesHeel_IRL

    postgres ate my ram again

Join the conversation on Fastr Chat