[ADMIN] Context-switch storm in 8.1.15

Hi everybody. Recently our company has been granted with a contract for an on-line store mainteinance. The website has been developed under J2EE and Postgres 8.1 as database backend. The system has been working without problem for several month, but with Christmas access to web portal has raised

[ADMIN] postgres block_size problem

Hi All, We were getting the following error on executing a COPY command on postgres8.2.0. SQL execution failed, Internal error. SQL Statement: (COPY command failed with error: ERROR: row is too big: size 8200, maximum size 8136) So, in order to fix the error we tried increasing the block size

Re: [ADMIN] rebellious pg stats collector (reopened case)

alive. Otherwise you'll have trouble with the collector not stopping when you want it to. Look into src/backend/storage/ipc/pmsignal.c: - return (getppid() == PostmasterPid); + return (getppid() != 1); (Obviously this is a hack, but it should work on any Unixish

Re: [ADMIN] postgres block_size problem

Bhujbal, Santosh wrote: Hi All, We were getting the following error on executing a COPY command on postgres8.2.0. SQL execution failed, Internal error. SQL Statement: (COPY command failed with error: ERROR: row is too big: size 8200, maximum size 8136) So, in order to fix the error we

Re: [ADMIN] postgres block_size problem

On Tue, Dec 30, 2008 at 5:28 AM, Bhujbal, Santosh sbhuj...@starentnetworks.com wrote: Hi All, We were getting the following error on executing a COPY command on postgres8.2.0. First and foremost, you need to run the latest version of 8.2, not 8.2.0. .0 releases of postgresql tend to have the

Re: [ADMIN] Context-switch storm in 8.1.15

On Tue, Dec 30, 2008 at 4:02 AM, Iñigo Martinez Lasala imarti...@vectorsf.com wrote: Hi everybody. Recently our company has been granted with a contract for an on-line store mainteinance. The website has been developed under J2EE and Postgres 8.1 as database backend. The system has been

Re: [ADMIN] postgres block_size problem

Scott Marlowe scott.marl...@gmail.com writes: On Tue, Dec 30, 2008 at 5:28 AM, Bhujbal, Santosh sbhuj...@starentnetworks.com wrote: SQL execution failed, Internal error. SQL Statement: (COPY command failed with error: ERROR: row is too big: size 8200, maximum size 8136) Hmmm. What exactly

Re: [ADMIN] postgres block_size problem

On Tue, Dec 30, 2008 at 12:56 PM, Tom Lane t...@sss.pgh.pa.us wrote: Scott Marlowe scott.marl...@gmail.com writes: On Tue, Dec 30, 2008 at 5:28 AM, Bhujbal, Santosh sbhuj...@starentnetworks.com wrote: SQL execution failed, Internal error. SQL Statement: (COPY command failed with error: ERROR:

Re: [ADMIN] ssl database connection problems...

Thanks to all of you. Many of my problems have been fixed. My listening_addresses was not set correctly. After I fixed that problem, I started getting an SSL error. I'm now getting this error as follows: walt...@fac-staff:~$ psql -U walterc -d walterc -h db -p 5433 psql: SSL SYSCALL

Re: [ADMIN] ssl database connection problems...

On Tue, Dec 30, 2008 at 03:53:37PM -0500, Carol Walter wrote: OpenSSL is telling me that ssl is not properly configured. how so? openssl verify -CAfile ./root.crt testcert.pem can you verify the server crt against the CA? That is the starting place. -- Sent via pgsql-admin mailing