Re: Access Problem After Version Upgrade -- Update
| От | Rich Shepard |
|---|---|
| Тема | Re: Access Problem After Version Upgrade -- Update |
| Дата | |
| Msg-id | Pine.LNX.4.63.0601260900500.3884@salmo.appl-ecosys.com обсуждение исходный текст |
| Ответ на | Access Problem After Version Upgrade (Rich Shepard <rshepard@appl-ecosys.com>) |
| Ответы |
Re: Access Problem After Version Upgrade -- Update
Re: Access Problem After Version Upgrade -- FIXED |
| Список | pgsql-general |
On Thu, 26 Jan 2006, Rich Shepard wrote:
> psql: could not connect to server: Permission denied
> What do I do to trace the source of this problem and fix it?
Some progress to report. A Google search found a reply from Tom Lane last
month to someone reporting the same error. I changed permissions on the
socket to make them world writable, and that fixed one problem:
[rshepard@salmo ~]$ psql -l
List of databases
Name | Owner | Encoding
-------------+------------+-----------
aesi | sql-ledger | LATIN1
eiabusiness | rshepard | SQL_ASCII
postgres | postgres | SQL_ASCII
template0 | postgres | SQL_ASCII
template1 | postgres | SQL_ASCII
test | postgres | SQL_ASCII
webcollab | rshepard | SQL_ASCII
(7 rows)
So, now I can see the tables in the various databases, but SQL-Ledger still
cannot:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable
to complete your request.
How do I get this fixed, please?
Rich
--
Richard B. Shepard, Ph.D. | Author of "Quantifying Environmental
Applied Ecosystem Services, Inc. (TM) | Impact Assessments Using Fuzzy Logic"
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
В списке pgsql-general по дате отправления: