| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Vladimir Ryabtsev <greatvovan(at)gmail(dot)com> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Why Postgres doesn't use TID scan? |
| Date: | 2018-12-19 11:41:27 |
| Message-ID: | 87bm5hwxy2.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>>>>> "Vladimir" == Vladimir Ryabtsev <greatvovan(at)gmail(dot)com> writes:
Vladimir> I can't believe it.
Vladimir> I see some recommendations in Internet to do like this
well, 90% of what you read on the Internet is wrong.
Vladimir> Did it really work in 2011? Are you saying they broke it?
Vladimir> It's a shame...
The method in that SO link does work, it's just slow. The workaround is
to do it like this instead:
delete from mytable
where ctid = any (array(select ctid from mytable
where ...
order by ...
limit 1000));
But of course that's still an ugly hack.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Ryabtsev | 2018-12-19 20:22:03 | Re: Why Postgres doesn't use TID scan? |
| Previous Message | Patrick Mulrooney | 2018-12-19 07:36:45 | Re: Increasing parallelism of queries while using file fdw and partitions |