how_to:vpop3_cannot_access_postgresql_-_timeout_expired
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous 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 [2018/11/14 10:45] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| 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. Note that this command may take a long time to run if it is this problem. |
| Also check the disk fragmentation, | Also check the disk fragmentation, | ||
how_to/vpop3_cannot_access_postgresql_-_timeout_expired.1390834968.txt.gz · Last modified: 2018/11/14 10:44 (external edit)
Page Tools
