Re: Sorting performance vs. MySQL
От | Greg Stark |
---|---|
Тема | Re: Sorting performance vs. MySQL |
Дата | |
Msg-id | 407d949e1002230102u1a374386h7aa5502839b965f@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Sorting performance vs. MySQL (Scott Marlowe <scott.marlowe@gmail.com>) |
Ответы |
Re: Sorting performance vs. MySQL
|
Список | pgsql-general |
On Tue, Feb 23, 2010 at 6:48 AM, Scott Marlowe <scott.marlowe@gmail.com> wrote: >> I'm relieved that Postgresql itself does not, in fact, suck, but >> slightly disappointed in the behavior of psql. I suppose it needs to >> buffer everything in memory to properly format its tabular output, >> among other possible reasons I could imagine. > > It's best when working with big sets to do so with a cursor and fetch > a few thousand rows at a time. It's how we handle really big sets at > work and it works like a charm in keeping the client from bogging down > with a huge memory footprint. > You can do \set FETCH_COUNT to have psql use a cursor automatically. -- greg
В списке pgsql-general по дате отправления: