Re: What is the fastest way to get a resultset
От | Bupp Phillips |
---|---|
Тема | Re: What is the fastest way to get a resultset |
Дата | |
Msg-id | big5vk$hg0$1@news.hub.org обсуждение исходный текст |
Ответ на | What is the fastest way to get a resultset ("Bupp Phillips" <hello@noname.com>) |
Ответы |
Re: What is the fastest way to get a resultset
|
Список | pgsql-performance |
Is this something that can be done thru a SQL statement, or are you saying that I need to develop logic to handle this because the database won't hold the resultset on the server, but instead sends it all to the client? It there a way to get server side cursors with Postgresql like SQLServer has or is this a limitation that it has? Thanks "Jeff" <threshar@torgo.978.org> wrote in message news:Pine.BSF.4.44.0308251645360.15800-100000@torgo.978.org... > On Mon, 25 Aug 2003, Bupp Phillips wrote: > > > > > I have a table that has 103,000 records in it (record size is about 953 > > bytes) and when I do a select all (select * from <table>) it takes a > > whopping 30 secs for the data to return!! > > > > SQLServer on the other hand takes 6 secs, but you can also use what is > > called a firehose cursor, which will return the data in < 1 sec. > > > You probably want a cursor. > Typically what happens is postgres sends _all_ the data to the client - > which can be rather substantial. A cursor allows you to say "get me the > first 1000 records. now the next 1000" - it should get you the speed you > want. > > > -- > Jeff Trout <jeff@jefftrout.com> > http://www.jefftrout.com/ > http://www.stuarthamm.net/ > > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org >
В списке pgsql-performance по дате отправления: