| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Amit Langote <amitlangote09(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: making update/delete of inheritance trees scale better |
| Date: | 2021-02-05 21:53:44 |
| Message-ID: | 137701.1612562024@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> As to why it causes us pain, I don't have a full picture of that.
> Target list construction is one problem: we build all these target
> lists for intermediate notes during planning and they're long enough
> -- if the user has a bunch of columns -- and planning is cheap enough
> for some queries that the sheer time to construct the list shows up
> noticeably in profiles.
Well, the tlist data structure is just about completely separate from
the TupleTableSlot mechanisms. I'm more prepared to believe that
we could improve on the former, though I don't have any immediate
ideas about how.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2021-02-05 21:54:58 | Re: More test/kerberos tweaks |
| Previous Message | Stephen Frost | 2021-02-05 21:22:34 | Re: automatic analyze: readahead - add "IO read time" log message |