| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vladimir Ryabtsev <greatvovan(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Why Postgres doesn't use TID scan? |
| Date: | 2018-12-18 02:32:51 |
| Message-ID: | 1247.1545100371@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Vladimir Ryabtsev <greatvovan(at)gmail(dot)com> writes:
> I see some recommendations in Internet to do like this (e.g.
> https://stackoverflow.com/questions/5170546/how-do-i-delete-a-fixed-number-of-rows-with-sorting-in-postgresql
> ).
> Did it really work in 2011?
No, or at least not any better than today. (For context, "git blame"
says I wrote the comment I just quoted to you in 2005. The feature it
says isn't there wasn't there before that, either.)
> Anyway I think the problem is pretty clear: I want to eventually clear the
> table based on the predicate but I don't want to lock it for a long time.
DELETE doesn't lock the whole table. What problem are you actually
facing?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Ryabtsev | 2018-12-18 02:40:49 | Re: Why Postgres doesn't use TID scan? |
| Previous Message | Vladimir Ryabtsev | 2018-12-18 01:54:19 | Re: Why Postgres doesn't use TID scan? |