On Nov 24, 2007 10:57 PM, <[EMAIL PROTECTED]> wrote:
> Hello,
>
>I forgot to say that I changed work_mem to 16 MB but I didn't have
> sucess.
> I received the same
> error message.
The error message you're getting is from your client because it's
getting too big of a result set back at onc
Hello,
I forgot to say that I changed work_mem to 16 MB but I didn't have sucess.
I received the same
error message.
Thanks,
Cláudia Amorim.
> Hi,
>
> When I set shared buffers higher than 1GB, PostGreSQL doens't start.
>
> When my application crashes I receive a message "Out of memory"
> It looks like the problem is that the UNION is taken as producing plain
> text output, as you can see with \d:
>
> regression=# \d foo
> Table "public.foo"
> Column | Type | Modifiers
> +--+---
> a | foo_text | not null
> b | text |
> Indexes:
> "foo_pkey" PRIMARY KEY, bt
Hi,
When I set shared buffers higher than 1GB, PostGreSQL doens't start.
When my application crashes I receive a message "Out of memory" or
"invalid sql statement". But the sql statement is ok - if I execute it
in a table with less registers, it works and it is very simple. When I monitor
the pr
[EMAIL PROTECTED] wrote:
I'm having serious peformance problems with PostGreSQL and Windows Server 2003
Enterprise Edition. The PostgreSQL Server don't starts if I set the shared
buffers high than
1GB. All my programs can use only 3 GB of RAM and I have 8GB of RAM.
When I try to execute a query i
