Re: [HACKERS] Another nasty cache problem

From: Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, prlw1(at)cam(dot)ac(dot)uk, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Another nasty cache problem
Date: 2000-02-04 04:39:59
Message-ID: 389A581F.47C0D822@nimrod.itg.telecom.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> With the fix I just committed, current sources execute the above query
> in constant backend memory space. psql's space usage still goes to the
> moon, of course, since it's trying to buffer the whole query result :-(
> ... but there's no way around that short of a major redesign of libpq's
> API. When and if we switch over to CORBA, we really need to rethink
> the client access API so that buffering the query result in the client-
> side library is an option not a requirement.

What about portals? Doesn't psql use portals?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-02-04 05:01:05 RE: [HACKERS] how to deal with sparse/to-be populated tables
Previous Message Tom Lane 2000-02-04 04:31:37 Re: [HACKERS] how to deal with sparse/to-be populated tables