| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
| Cc: | "Dirschel, Steve" <steve(dot)dirschel(at)thomsonreuters(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [EXT] Re: Troubleshooting a long running delete statement |
| Date: | 2021-10-07 19:30:11 |
| Message-ID: | CADkLM=c8TNqEM4ZATNq5Q-nGV7wrNeSY3s8By+x61HkFT=_r7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>
>
>
> This won't be immediately useful, but there's been a patch proposed for
> Postgres 15 to allow logging the plan of a running query [1]. Progress
> seems to have stalled a bit, but it seems like there was a fair amount of
> interest, so I wouldn't count it out yet. If you have thoughts on the
> proposed functionality, I'm sure thoughtful feedback would be appreciated.
>
>
>
Didn't something get into v14 about doing ctd range scans, which would
allow you to break up a large update/delete into chunks, so you wouldn't do
a full seq scan, but you also would avoid needing an index as a proxy for
batching records?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2021-10-08 01:09:08 | Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle |
| Previous Message | Maciek Sakrejda | 2021-10-07 05:15:36 | Re: [EXT] Re: Troubleshooting a long running delete statement |