On Tue, Feb 9, 2010 at 1:55 PM, John R Pierce wrote:
> Guillaume Lelarge wrote:
>>>
>>> is this a 64bit postgres build?
>>>
>>> if not, you're probably running out of virtual address space in the 32
>>> bit user space, which is limited to like 2gb.
>>>
>>>
>>
>> IIRC, the virtual address space in
Guillaume Lelarge wrote:
is this a 64bit postgres build?
if not, you're probably running out of virtual address space in the 32
bit user space, which is limited to like 2gb.
IIRC, the virtual address space in 32bit platforms is 4GB.
it is, but within that 4gb, the kernel uses the to
Magnus Hagander wrote:
On Tue, Feb 9, 2010 at 09:53, David Kerr wrote:
Guillaume Lelarge wrote:
Le 09/02/2010 09:35, David Kerr a écrit :
Guillaume Lelarge wrote:
Le 09/02/2010 05:49, John R Pierce a écrit :
David Kerr wrote:
maintenance_work_mem = 1GB
So evidently, when it tries to actua
On Tue, Feb 9, 2010 at 09:53, David Kerr wrote:
> Guillaume Lelarge wrote:
>>
>> Le 09/02/2010 09:35, David Kerr a écrit :
>>>
>>> Guillaume Lelarge wrote:
Le 09/02/2010 05:49, John R Pierce a écrit :
>
> David Kerr wrote:
maintenance_work_mem = 1GB
>>>
Guillaume Lelarge wrote:
Le 09/02/2010 09:35, David Kerr a écrit :
Guillaume Lelarge wrote:
Le 09/02/2010 05:49, John R Pierce a écrit :
David Kerr wrote:
maintenance_work_mem = 1GB
So evidently, when it tries to actually allocate 1GB, it can't do it.
Ergo, that setting is too high for your
Le 09/02/2010 09:35, David Kerr a écrit :
> Guillaume Lelarge wrote:
>> Le 09/02/2010 05:49, John R Pierce a écrit :
>>> David Kerr wrote:
>> maintenance_work_mem = 1GB
> So evidently, when it tries to actually allocate 1GB, it can't do it.
> Ergo, that setting is too high for your mach
Guillaume Lelarge wrote:
Le 09/02/2010 05:49, John R Pierce a écrit :
David Kerr wrote:
maintenance_work_mem = 1GB
So evidently, when it tries to actually allocate 1GB, it can't do it.
Ergo, that setting is too high for your machine.
...
seems like i've got 2GB free.
is this a 64bit postgre
Le 09/02/2010 05:49, John R Pierce a écrit :
> David Kerr wrote:
maintenance_work_mem = 1GB
>>>
>>> So evidently, when it tries to actually allocate 1GB, it can't do it.
>>> Ergo, that setting is too high for your machine.
>>> ...
>>
>> seems like i've got 2GB free.
>
>
> is this a 64bit pos
David Kerr wrote:
maintenance_work_mem = 1GB
So evidently, when it tries to actually allocate 1GB, it can't do it.
Ergo, that setting is too high for your machine.
...
seems like i've got 2GB free.
is this a 64bit postgres build?
if not, you're probably running out of virtual address spa
Tom Lane wrote:
David Kerr writes:
Tom Lane wrote:
David Kerr writes:
I get:
vacuumdb: vacuuming of database "assessment" failed: ERROR: out of memory
DETAIL: Failed on request of size 1073741820.
What have you got maintenance_work_mem set to?
maintenance_work_mem = 1GB
So evidently,
David Kerr writes:
> Tom Lane wrote:
>> David Kerr writes:
>>> I get:
>>> vacuumdb: vacuuming of database "assessment" failed: ERROR: out of memory
>>> DETAIL: Failed on request of size 1073741820.
>>
>> What have you got maintenance_work_mem set to?
> maintenance_work_mem = 1GB
So evidently
Tom Lane wrote:
David Kerr writes:
I'm getting error:
When I try
vacuumdb -z assessment
or
vacuumdb assessment
I get:
vacuumdb: vacuuming of database "assessment" failed: ERROR: out of memory
DETAIL: Failed on request of size 1073741820.
What have you got maintenance_work_mem set to?
David Kerr writes:
> I'm getting error:
> When I try
> vacuumdb -z assessment
> or
> vacuumdb assessment
> I get:
> vacuumdb: vacuuming of database "assessment" failed: ERROR: out of memory
> DETAIL: Failed on request of size 1073741820.
What have you got maintenance_work_mem set to?
13 matches
Mail list logo
