Denis Vlasenko wrote:
Symptom: even the simplest query
$result = pg_query($db, "SELECT * FROM big_table");
eats enormous amounts of memory on server
(proportional to table size).
Right, which is exactly what you would expect. The entire result set is
sent to the client and stored in local memo
Satoshi Nagayasu <[EMAIL PROTECTED]> writes:
> When I attempted to create a trigger function with argument(s),
> the backend got crashed.
> Is this a bug, or just my mistake(or misunderstanding)?
Definitely a bug; existing releases don't do that. Thanks for the
report.
re
Satoshi Nagayasu wrote:
> Hi all,
>
> When I attempted to create a trigger function with argument(s),
> the backend got crashed.
>
> I know this operation is wrong, however I think the backend crash
> mustn't be occured, it should be a syntax error or something like that.
>
> Is this a bug, or j
Denis,
$result = pg_query($db, "SELECT * FROM big_table");
you are reading a big result (as I suspect from big_table) into memory.
It is perfectly normal that this uses large amounts of memory.
[it would be rather suspicious if loading a big file / big resultset would not use big amounts of memo
On Wed, Jul 06, 2005 at 05:59:24PM +0900, Satoshi Nagayasu wrote:
>
> When I attempted to create a trigger function with argument(s),
> the backend got crashed.
Same here with the most recent HEAD. Here's a stack trace:
#0 0xfed2f648 in plpgsql_compile (fcinfo=0xffbfdf38, forValidator=-32 'à')
The following bug has been logged online:
Bug reference: 1756
Logged by: Denis Vlasenko
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Linux
Description:PQexec eats huge amounts of memory
Details:
Verbatim from http://bugs.php.net/bug.p
Hi all,
When I attempted to create a trigger function with argument(s),
the backend got crashed.
I know this operation is wrong, however I think the backend crash
mustn't be occured, it should be a syntax error or something like that.
Is this a bug, or just my mistake(or misunderstanding)?
Now
Hi,
when I run: ./configure --without-readline, I get errors that aborts the configure
process: "checking types of arguments for accept()...
configure: error: could not determine argument types".
Please see following from the config.log.
Thanks,
Thanh
configure:10983: gcc -c -O2 -fno-stric