network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 6 months |
| seen | Apr 12 at 9:01 | |
| stats | profile views | 1 |
|
Mar 12 |
awarded | Scholar |
|
Mar 12 |
comment |
What fillfactor for caching table? I think UNLOGGED is exactly what I need |
|
Mar 12 |
accepted | What fillfactor for caching table? |
|
Mar 11 |
asked | What fillfactor for caching table? |
|
Jan 27 |
awarded | Teacher |
|
Nov 26 |
comment |
How to determine why connection creation lasts so long? in PostgreSQL .conf file. It's disabled by default. |
|
Nov 26 |
answered | How to determine why connection creation lasts so long? |
|
Nov 23 |
comment |
How to determine why connection creation lasts so long? It's Windows 2008, not linux. You can believe or not, turning off SSL resulted in shortening acquiring connection time and general SQL queries time :) Weird, but I am happy I am through it already. |
|
Nov 22 |
comment |
How to determine why connection creation lasts so long? I answer myself - it was SSL set to on. |
|
Nov 21 |
asked | How to determine why connection creation lasts so long? |
|
Nov 17 |
awarded | Student |
|
Nov 15 |
asked | Archive database on Postgres |
|
Nov 15 |
comment |
Long disk queue when no traffic I don't think it's autovacuum, but maybe... I enabled checkpoint logging as it was missing before. |
|
Nov 14 |
asked | Long disk queue when no traffic |
|
Nov 8 |
comment |
Postgres not vacuuming 1 table It's Postgres 9.1 Yes, there are connections in transaction, but not all the time, so there should be plenty of time for vacuum. I never applied any table-specific autovacuum settings. SHOW max_prepared_transactions = 0 SELECT count(*) FROM pg_prepared_xacts = 0 |
|
Nov 8 |
asked | Postgres not vacuuming 1 table |
