Re: ctid ranges
От | Merlin Moncure |
---|---|
Тема | Re: ctid ranges |
Дата | |
Msg-id | CAHyXU0zJhg_5RtxKnNbAK=4ZzQEFUFi+52RjpLrxtkRTD6CDFw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ctid ranges (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: ctid ranges
|
Список | pgsql-general |
On Wed, Jun 13, 2012 at 3:18 PM, Bruce Momjian <bruce@momjian.us> wrote: > On Wed, Jun 13, 2012 at 03:15:14PM -0500, Merlin Moncure wrote: >> 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. > > Can we add this as a TODO? It would basically be adding > less/greater-than comparisons for the 'tid' data type. IMNSHO, it's a no-brainer for the todo (but I think it's more complicated than adding some comparisons -- which are working now): postgres=# explain select ctid from foo where ctid >= '(3786,67)'::tid limit 1; QUERY PLAN ------------------------------------------------------------------ Limit (cost=0.00..0.05 rows=1 width=6) -> Seq Scan on foo (cost=0.00..16422.00 rows=333333 width=6) Filter: (ctid >= '(3786,67)'::tid) (3 rows) merlin
В списке pgsql-general по дате отправления: