| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Thomas Munro <munro(at)ip9(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ctid ranges |
| Date: | 2012-06-13 20:15:14 |
| Message-ID: | CAHyXU0wMyS1U2HdfdRkjMAfJro-u-bHodvD5AD_2p_M2ysWv5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jun 11, 2012 at 7:57 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Fri, 2012-06-08 at 22:27 +0100, Thomas Munro wrote:
>> This is slow, handled with a seq scan (as are various rephrasing with
>> <, <=, etc):
>>
>> SELECT ... FROM ... WHERE ctid BETWEEN ... AND ...;
>>
>> Is there a way to retrieve the rows in a physical range quickly?
>
> Interesting idea. However, as far as I know, there is no such support.
yeah -- and I think it's a great thing to want to be able to do. it
could be used in parallelizing tricks for example: divide up a table
into N approximately equal parts and hand each one off to a work
thread.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2012-06-13 20:18:16 | Re: ctid ranges |
| Previous Message | Merlin Moncure | 2012-06-13 19:32:36 | Re: composite type use in pl/gpsql |