Re: Alternate or Optimization for with hold cursor

Поиск
Список
Период
Сортировка
Искать
От
Rakesh Kumar
Тема
Re: Alternate or Optimization for with hold cursor
Дата
в 11:25:13
Msg-id
8922C03A-92CE-49B7-98EB-EB55FCAECA40@gmail.com
Ответ на
Список
Дерево обсуждения
Alternate or Optimization for with hold cursor sangeetha <tune2sangee@gmail.com>
Re: Alternate or Optimization for with hold cursor "Mike Sofen" <msofen@runbox.com>
Re: Alternate or Optimization for with hold cursor amulsul <sul_amul@yahoo.co.in>
Re: Alternate or Optimization for with hold cursor Rakesh Kumar <rakeshkumar464a3@gmail.com>

On May 12, 2016, at 4:57 AM, sangeetha  wrote:

Currently , I am using "With hold" cursor. In our case , the With hold cursor
is used to fetch the next record of the given primary key . 

Can you explain your use case. If i understand with hold correctly, it is typically used to preserve locks even after commit , so as to get a consistent view of data. 


The performance
is very slow for large data set. Can you provide me some alternative ways
like having own copy of table , or optimization for With hold cursor?

Thanks and Regards,
S.Sangeetha



--
View this message in context: http://postgresql.nabble.com/Alternate-or-Optimization-for-with-hold-cursor-tp5903211.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

В списке pgsql-general по дате отправления
От: sangeetha
Дата:
От: Adam Pearson
Дата:
Сообщение: Re: NULL concatenation
FAQ