WARNING: out of shared memory
We are working on Windows Server 2003 Enterprise with PostgreSQL 8.4, when
we start populating a table with 130,000 records it start giving "WARNING:
out of shared memory"
on every record that was inserted. At the end it did not finish, it only
inserted 4,000 records and got the following message:
2009-07-16 16:54:05 EDT WARNING: worker took too long to start;
cancelled
2009-07-16 16:54:05 EDT WARNING: out of shared memory
2009-07-16 16:54:05 EDT FATAL: out of shared memory
Also, we are not able to login to the database with PgAdmin, getting same
error "out of shared memory"
Once we stop and start the service, we were able to access the database
again.
Any ideas what is going wrong?
Thanks,
Juan C.
Attachments:
On Thu, Jul 16, 2009 at 4:41 PM, Juan C. Aragon<juan@keisercomputers.com> wrote:
We are working on Windows Server 2003 Enterprise with PostgreSQL 8.4, when
we start populating a table with 130,000 records it start giving “WARNING:
out of shared memory”on every record that was inserted. At the end it did not finish, it only
inserted 4,000 records and got the following message:2009-07-16 16:54:05 EDT WARNING: worker took too long to start;
cancelled2009-07-16 16:54:05 EDT WARNING: out of shared memory
2009-07-16 16:54:05 EDT FATAL: out of shared memory
but this, is a different thing...
how much memory you have in your machine? and how much has been
assigned to postgres via shared_buffers?
can you show a self contained example of this (eg: the minimun
structure of the table and the inserts you need to make the bug
happen)?
Also, we are not able to login to the database with PgAdmin, getting same
error “out of shared memory”
what's the value in max_connections?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
cc: the -list this time
---------- Forwarded message ----------
From: Jaime Casanova <jcasanov@systemguards.com.ec>
Date: Thu, Jul 16, 2009 at 5:18 PM
Subject: Re: [BUGS] WARNING: out of shared memory
To: "Juan C. Aragon" <juan@keisercomputers.com>
it's better for you to always write to the list because there are more
people that can help and the most of them are more prepared than me :)
On Thu, Jul 16, 2009 at 5:05 PM, Juan C. Aragon<juan@keisercomputers.com> wrote:
Yes, this is another server.
There is 8GB of memory.
max_connections = 100
shared_buffers = 32MB
well, you are plenty of RAM and thats seems a default configuration...
you can raise it to something better like 2GB...
that doesn't explain the error, though... at least not to me
It looks like this:
2009-07-16 16:53:20 WARNING: out of shared memory
2009-07-16 16:53:20 STATEMENT: INSERT INTO "public"."student_table" (
student_first_name,student_last_name,student_address,student_city,student_st
ate,student_zip,student_phone,student_email,student_dob,student_status,sycam
pusid,campus_name,student_address2,student_sex,student_mi,student_work_phone
,student_ssn,datelstmod,syschoolstatusid,systudentid,dlstate,dlnumber,alienn
um,balover10k,balover5k)
2009-07-16 16:53:20 ERROR: out of shared memory
i can't make an example with this... where's the value clause... what
were you inserting?
There is only one table.
great! can you share (if you prefer in private, yes i'm the same that
makes the above comment ;) the structure of that single table and if
you can the inserts that are executing... what i'm looking for is what
is triggering that error and if it's something we can repeat in other
environments (say something less evil like linux)
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
Import Notes
Reply to msg id not found: 3073cc9b0907161518r20500797y3041909d2cbbfe0b@mail.gmail.com
"Juan C. Aragon" <juan@keisercomputers.com> writes:
2009-07-16 16:54:05 EDT WARNING: out of shared memory
2009-07-16 16:54:05 EDT FATAL: out of shared memory
You might be running out of lock-table space ... does raising
max_locks_per_transaction help? (Note you need a postmaster restart
to change that.)
regards, tom lane