| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jonathan Katz <jkatz(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Subject: | Re: Improving connection scalability: GetSnapshotData() |
| Date: | 2020-04-07 18:32:42 |
| Message-ID: | CAH2-WznuZD9QxFzWGd6Czz_89gpO=2+TEa84ZJibibWhtTh8Ww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 7, 2020 at 11:28 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> There is a lot of code that is pretty unsafe around wraparounds... They
> are getting easier and easier to hit on a regular schedule in production
> (plenty of databases that hit wraparounds multiple times a week). And I
> don't think we as PG developers often don't quite take that into
> account.
It would be nice if there was high level documentation on wraparound
hazards. Maybe even a dedicated README file.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-04-07 18:51:52 | Re: Improving connection scalability: GetSnapshotData() |
| Previous Message | Andres Freund | 2020-04-07 18:28:52 | Re: Improving connection scalability: GetSnapshotData() |