| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: POC: converting Lists into arrays |
| Date: | 2019-03-04 22:08:36 |
| Message-ID: | CAH2-Wz=bLMnTM0SHDvrdBXdRom2XZrXxZvcS8SaFLMOfQTFkzg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 4, 2019 at 2:04 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Mon, Mar 4, 2019 at 12:44:41PM -0500, Robert Haas wrote:
> > I think that's a separate but also promising thing to attack, and I
> > agree that it'd take a lot of work to get there. I don't think that
> > the problem with either parse-tree-copying or list usage is that no
> > performance benefits are to be had; I think it's that the amount of
> > work required to get those benefits is pretty large. If it were
> > otherwise, somebody likely would have done it before now.
>
> Stupid question, but do we use any kind of reference counter to know if
> two subsystems look at a structure, and a copy is required?
No, but I wonder if we could use Valgrind to enforce rules about who
has the right to scribble on what, when. That could make it a lot
easier to impose a new rule.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jerry Jelinek | 2019-03-04 22:09:00 | Re: patch to allow disable of WAL recycling |
| Previous Message | Bruce Momjian | 2019-03-04 22:08:26 | Re: POC: converting Lists into arrays |