Re: Release SPI plans for referential integrity with DISCARD ALL

From: yuzuko <yuzukohosoya(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Release SPI plans for referential integrity with DISCARD ALL
Date: 2021-01-25 06:10:56
Message-ID: CAKkQ50_h8TcBkY5KYQfneejrZ_d3veFcK3nGmN-WxucEu_QrCw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

Thank you for your comments.
Following Corey's advice, I applied Amit's patches proposed in this
email [1], and confirmed our memory pressure problem was solved.
So dropping cached plan with DISCARD is not necessary anymore.

[1] https://www.postgresql.org/message-id/CA%2BHiwqG1qQuBwApueaUfA855UJ4TiSgFkPF34hQDWx3tOChV5w%40mail.gmail.com

--
Best regards,
Yuzuko Hosoya
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Nancarrow 2021-01-25 06:47:41 Re: Parallel INSERT (INTO ... SELECT ...)
Previous Message Amit Kapila 2021-01-25 05:48:41 Re: Single transaction in the tablesync worker?