This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
how_to:vpop3_cannot_access_postgresql_-_timeout_expired [2014/01/27 15:02] – [Possible causes] paul | how_to:vpop3_cannot_access_postgresql_-_timeout_expired [2014/03/04 13:24] – [Possible causes] paul | ||
---|---|---|---|
Line 17: | Line 17: | ||
One cause we have found is if the **pg_attribute** table in the database is too large. A known problem with the version of PostgreSQL shipped with VPOP3 (9.1.1) is that if this table is very large, it may take an exceptionally long time for PostgreSQL to start. | One cause we have found is if the **pg_attribute** table in the database is too large. A known problem with the version of PostgreSQL shipped with VPOP3 (9.1.1) is that if this table is very large, it may take an exceptionally long time for PostgreSQL to start. | ||
- | You can check if this is the problem. Wait until PostgreSQL has started, then from a command prompt in the VPOP3 directory run | + | You can check if this is the problem. Wait until PostgreSQL has started, then from a command prompt in the VPOP3\pgsql\bin |
- | psql -c " | + | psql -U postgres -p 5433 -c " |
- | (the password is 'vpop3pass') | + | (the password is 'pgsqlpass') |
| | ||
If the displayed value is over about 100,000, then this may be the problem. Contact support@pscs.co.uk for assistance. | If the displayed value is over about 100,000, then this may be the problem. Contact support@pscs.co.uk for assistance. |