| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Subject: | Re: Improving connection scalability: GetSnapshotData() |
| Date: | 2020-08-16 21:28:02 |
| Message-ID: | CAH2-WzkuTcB2WbegRicnaVQ+igBsDP3AQawivEunEGR3m1vs0w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Aug 16, 2020 at 2:11 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> For the first, one issue is that there's no obviously good candidate for
> an uninitialized xid. We could use something like FrozenTransactionId,
> which may never be in the procarray. But it's not exactly pretty.
Maybe it would make sense to mark the fields as inaccessible or
undefined to Valgrind. That has advantages and disadvantages that are
obvious.
If that isn't enough, it might not hurt to do this on top of whatever
becomes the primary solution. An undefined value has the advantage of
"spreading" when the value gets copied around.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-08-16 21:28:46 | Re: Improving connection scalability: GetSnapshotData() |
| Previous Message | Andres Freund | 2020-08-16 21:26:57 | Re: Improving connection scalability: GetSnapshotData() |