|
View:
New views
2 Messages
—
Rating Filter:
Alert me
|
|
|
[Problem] - Error: cannot open pg_class_oid_index: Permission deniedHi, This is Selva from Actually my application is using the postgres 7.2.4
as backend. Around 8 client consoles will be connecting and
making the transactions to one of the tables in the database. We started all 8 machines and made automatic
transactions for every one minute from all the machines to the database. Machines were running without any problem for 2 days
(without shutting down the machines). After 2 days 6 of the machines were hung since they
were not able to establish a connection with the table. At the point of time, number of records in the table
is 35000. (Vaccum is not happening) But other 2 machines are working fine. Errors are as below: Mac 1: At 6:51:15 - ERROR:
cannot open pg_class_oid_index: Permission denied Mac
2: At 6:51:45 – ERROR:
cannot open pg_class_oid_index: Permission denied Mac
3: At 6:53:54 - FATAL 1:
cannot open pg_attribute: Permission denied Max connections configured in the database is 60 Shared buffer 256 Our application will use around 2 connections each
machine. Plus 1 connection will be opened and closed for every transaction. Please let me know what exactly is the problem and
how it can be solved. Thanks in advance, Selva
|
|
|
|
Re: [Problem] - Error: cannot open pg_class_oid_index: Permission denied"Selvakaruppiah s-TLS,Chennai" <Selvakaruppiahs@...> writes:
> Actually my application is using the postgres 7.2.4 as backend. [ blink... ] Please tell us that is a typo. 7.2.4 is more than five years old, and the entire 7.2 branch was abandoned as unfixably buggy and insecure more than three years ago. If you're using a software distribution that presents 7.2.4 as a current version, then you have equally bad problems for every other part of that distribution. > Mac 1: At 6:51:15 - ERROR: cannot open pg_class_oid_index: Permission denied The only cause I've heard of for sudden occurrences of "permission denied" errors on databases that had been working is interference of broken Windows antivirus software. If you're running 7.2 atop Cygwin atop Windows (which is the only way 7.2 could have run on Windows) then you really are working with a house of cards --- get yourself to a native PG install using recent 8.2.x or 8.3.x. Your AV software will still be just as broken though, so you likely also need to update or remove it. (Dare I suggest installing a real operating system instead of M$?) regards, tom lane -- Sent via pgsql-novice mailing list (pgsql-novice@...) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-novice |
| Free Forum Powered by Nabble | Forum Help |