Re: Clarification reqeusted for "select * from a huge table" - Mailing list pgsql-hackers

From Trevor Talbot
Subject Re: Clarification reqeusted for "select * from a huge table"
Date
Msg-id 90bce5730711120510u1a3fd3aav60b4c97159da911c@mail.gmail.com
Whole thread Raw
In response to Re: Clarification reqeusted for "select * from a huge table"  (Richard Huxton <dev@archonet.com>)
Responses Re: Clarification reqeusted for "select * from a huge table"  (Richard Huxton <dev@archonet.com>)
List pgsql-hackers
On 11/12/07, Richard Huxton <dev@archonet.com> wrote:
> Gokulakannan Somasundaram wrote:

> >>>     I also noticed that it doesn't crash with psql, but it takes a
> >>> long time to show the first set of records. It takes a long time, even
> >>> to quit after i pressed 'q'.
> >>>    With oracle SQLPlus, it is quite instantaneous.

> > Imagine, you need a large batch operation. In oracle we can fire the
> > SQL and we can be sure that the client won't crash, but with postgres
> > we have a region of uncertainity.
>
> Well, if your client doesn't know if it can handle 1 million rows, maybe
> it shouldn't ask for them?

Isn't that exactly his point?  He's talking about the default behavior
of clients designed for postgres, one of which is psql.


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [hibernate-team] PostgreSQLDialect
Next
From: Bernd Helmle
Date:
Subject: Re: Clarification reqeusted for "select * from a huge table"