| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Trevor Talbot <quension(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Clarification reqeusted for "select * from a huge table" |
| Date: | 2007-11-12 14:16:40 |
| Message-ID: | 47386048.8000205@archonet.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Trevor Talbot wrote:
> On 11/12/07, Richard Huxton <dev(at)archonet(dot)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.
Psql isn't the client - you are.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Dunstan | 2007-11-12 14:35:40 | Re: [hibernate-team] PostgreSQLDialect |
| Previous Message | Andrew Dunstan | 2007-11-12 14:13:37 | Re: [hibernate-team] PostgreSQLDialect |