Re: PostgreSQL query failed: COPY state must be terminated first

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Shane Wright <me(at)shanewright(dot)co(dot)uk>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: PostgreSQL query failed: COPY state must be terminated first
Date: 2002-10-17 23:19:35
Message-ID: 20021017231934.GA18644@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 17, 2002 at 04:59:48PM +0100, Shane Wright wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi
>
> Thanks, that sounds plausible. However IIRC 7.1.x doesn't have cursors :(

Even 7.0.x had cursors, dunno before that.

> It would be prohibitively complex to try to rework the queries - is there a
> particular memory chunk its likely to be (and how to increase whats
> available?) The server isn't short of RAM so should be a reasonable
> workaround for now.

The result is stored on the *client* side, not the server. The result
reaches the client and will simply keep growing. I've accedently made
results sets several gig in size and no amount of memory will fix that.

--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> There are 10 kinds of people in the world, those that can do binary
> arithmetic and those that can't.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Roberto (SmartBit) 2002-10-18 00:45:50 Finding a value in an array field
Previous Message Paul 2002-10-17 22:46:26 replication