Re: [ADMIN] increasing of the shared memory does not solve the problem of "OUT of shared memory"

"Sorin N. Ciolofan" <[EMAIL PROTECTED]> writes: > Also I increased the max_locks_per_transaction from 64 to 10 000. > I still receive the same error form Postgres: > org.postgresql.util.PSQLException: ERROR: out of shared memory Did you remember to restart the postmaster after doing that? (pg_

Re: [ADMIN] increasing of the shared memory does not solve the problem of "OUT of shared memory"

> I increased significantly the number of shared buffers from 3000 to > 100 000 (80Mb) > Also I increased the max_locks_per_transaction from 64 to 10 000. > I still receive the same error form Postgres: > org.postgresql.util.PSQLException: ERROR: out of shared memory > Is this message appropria

[ADMIN] increasing of the shared memory does not solve the problem of "OUT of shared memory"

Hello! I increased significantly the number of shared buffers from 3000 to 100 000 (80Mb) Also I increased the max_locks_per_transaction from 64 to 10 000. I still receive the same error form Postgres: org.postgresql.util.PSQLException: ERROR: out of shared memory Is this message approp

Re: [ADMIN] duplicate key violates unique constraint

> From: Tom Lane [mailto:[EMAIL PROTECTED] > > "Spiegelberg, Greg" <[EMAIL PROTECTED]> writes: > > As you can see, it's only providing the key1 column and the > sequence is > > providing the value for the column with the constraint. > How can this be > > happening? > > Perhaps at some point y

Re: [ADMIN] duplicate key violates unique constraint

Yes, I've seen "serial" used in other places than the primary key, but I was referring to Greg's output. The data type for the sequence is listed as "bigint". My thought was that the data type was listed as "serial" for sequences. I just looked at my database and I was wrong about that.