Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
AndresFreundTec's profile
Andres Freund (Tech)
Andres Freund (Tech)
Andres Freund (Tech)
@AndresFreundTec

Tweets

Andres Freund (Tech)

@AndresFreundTec

Postgres developer, working at Microsoft. Also: politics nerd, expat German in the US. Account for tech related things. For politics: @AndresFreundPol

San Francisco, CA
Joined August 2017

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Peter Geoghegan‏ @petervgeoghegan 5 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @postgresmen

      I've seen things like this happen before. Usually something like a buggy hand-rolled upsert procedure (with improper handling of duplicate violation) is involved. That can burn through transaction IDs very quickly, without a true spike in writes.

      1 reply 1 retweet 5 likes
    2. Peter Geoghegan‏ @petervgeoghegan 5 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @petervgeoghegan @postgresmen

      That speculation could be wrong, of course -- it's just something I've observed during similar production outages. Even if I'm right, that's not a great failure mode.

      1 reply 0 retweets 1 like
    3. Lætitia‏ @l_avrot 8 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @petervgeoghegan @postgresmen

      Is there a great failure mode?

      3 replies 0 retweets 0 likes
    4. Christophe Pettus‏ @Xof 8 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @l_avrot @petervgeoghegan @postgresmen

      I would guess that they either disabled autovacuum, or had some other operation (like manual locking) going on that was preventing autovacuum from completing.

      1 reply 0 retweets 0 likes
    5. Peter Geoghegan‏ @petervgeoghegan 8 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Xof @l_avrot @postgresmen

      Sounds very plausible. In cases like this, it's often a combination of something like a TRUNCATE cron job, and anti-wraparound autovacuum (not regular av). Often an unlucky confluence of issues that are individually not very problematic. Good example:https://www.joyent.com/blog/manta-postmortem-7-27-2015 …

      1 reply 0 retweets 0 likes
    6. Peter Geoghegan‏ @petervgeoghegan 8 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @petervgeoghegan @Xof and

      Why did somebody write a cron job to periodically TRUNCATE the events table? To stop getting those annoying anti-wrapraround vacuums every few weeks!

      1 reply 0 retweets 0 likes
    7. Christophe Pettus‏ @Xof 8 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @petervgeoghegan @l_avrot @postgresmen

      I've seen a cron job that explicitly queried pg_stat_activity, and then did a pg_terminate_backend() on "(to prevent xid wraparound)" autovacuums because they were "causing so much I/O."

      1 reply 0 retweets 2 likes
    8. Peter Geoghegan‏ @petervgeoghegan 8 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @Xof @l_avrot @postgresmen

      That's something that I haven't seen, and cannot one-up :-)

      1 reply 0 retweets 0 likes
    9. Vik Fearing‏ @pg_xocolatl 9 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @petervgeoghegan @Xof and

      You're lucky. I've seen it several times.

      1 reply 0 retweets 1 like
    10. Magnus Hagander‏ @magnushagander 10 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pg_xocolatl @petervgeoghegan and

      Yeah, same here. It's one of the new versions of the good old "replication stops working when my scheduled job to drop and recreate tables (to make sure they are efficient) runs" from back in the trigger replication days

      1 reply 0 retweets 2 likes
      Andres Freund (Tech)‏ @AndresFreundTec 10 Feb 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @magnushagander @pg_xocolatl and

      I've seen people complain about too much WAL being generated - turns out they did "VACUUM FULL;" multiple times a day.

      12:49 AM - 10 Feb 2019
      • 5 Likes
      • Julien Rouhaud think(x) Hans-Jürgen Schönig Lætitia Nikolay Samokhvalov
      2 replies 0 retweets 5 likes
        1. New conversation
        2. Nikolay Samokhvalov‏ @postgresmen 10 Feb 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @AndresFreundTec @magnushagander and

          ^^ @the_hydrobiont good additions to your collection of Postgres horror stories

          1 reply 0 retweets 1 like
        3. hydrobiont‏ @the_hydrobiont 10 Feb 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @postgresmen @AndresFreundTec and

          many of them are already there;)

          0 replies 0 retweets 1 like
        4. End of conversation
        1. Magnus Hagander‏ @magnushagander 10 Feb 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @AndresFreundTec @pg_xocolatl and

          I've seem people do that but they have complained mostly about vacuum locking things than wal volume. But yeah....

          0 replies 0 retweets 2 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info