Re: PostgreSQL query failed: COPY state must be terminated first
От | Shane Wright |
---|---|
Тема | Re: PostgreSQL query failed: COPY state must be terminated first |
Дата | |
Msg-id | 200210171659.48694.me@shanewright.co.uk обсуждение исходный текст |
Ответ на | Re: PostgreSQL query failed: COPY state must be terminated first (Jeff Eckermann <jeff_eckermann@yahoo.com>) |
Ответы |
Re: PostgreSQL query failed: COPY state must be terminated first
Re: PostgreSQL query failed: COPY state must be terminated first |
Список | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Thanks, that sounds plausible. However IIRC 7.1.x doesn't have cursors :( 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. Thanks Shane On Thursday 17 October 2002 2:58 pm, Jeff Eckermann wrote: > This kind of error usually indicates that your result > set has exceeded the available memory. I think the > "COPY" message is just noise. > The workaround would be to declare your query as a > cursor, and fetch the results in manageable chunks. - -- Shane http://www.shanewright.co.uk/ Public key: http://www.shanewright.co.uk/files/public_key.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9rt505DXg6dCMBrQRAgyQAKDC/FPOms8mwd+PgLSqkl5u5SoJcwCeKXeh T/7JHmvzRk4Me687TJgq6BU= =WeS6 -----END PGP SIGNATURE-----
В списке pgsql-general по дате отправления: