From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Temporary tables versus wraparound... again |
Date: | 2022-11-02 13:54:54 |
Message-ID: | CAM-w4HOvqQB=VvZBqCJ45ZhynzqCWG24UBj8LaPgEg9Nh_Ff4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 8 Nov 2020 at 18:19, Greg Stark <stark(at)mit(dot)edu> wrote:
>
> We had an outage caused by transaction wraparound. And yes, one of the
> first things I did on this site was check that we didn't have any
> databases that were in danger of wraparound.
Fwiw this patch has been in "Ready for Committer" state since April
and has been moved forward three times including missing the release.
It's a pretty short patch and fixes a problem that caused an outage
for $previous_employer and I've had private discussions from other
people who have been struggling with the same issue. Personally I
consider it pretty close to a bug fix and worth backpatching. I think
it's pretty annoying to have put out a release without this fix.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Zhihong Yu | 2022-11-02 14:04:37 | restoring user id and SecContext before logging error in ri_PlanCheck |
Previous Message | Justin Pryzby | 2022-11-02 13:28:03 | Re: Add LZ4 compression in pg_dump |