| bio | website | |
|---|---|---|
| location | ||
| age | 29 | |
| visits | member for | 7 months |
| seen | Apr 30 at 20:32 | |
| stats | profile views | 3 |
|
Oct 25 |
comment |
Does updating a partially indexed field add or remove it from an index in Postgres Here's a cleaned version of the IRC conversation referenced above. It was from the #postgresql channel on the freenode IRC network, there are very helpful people in there! (also updated my name on here to match my IRC handle, to avoid confusion). |
|
Oct 25 |
accepted | Does updating a partially indexed field add or remove it from an index in Postgres |
|
Oct 25 |
comment |
Does updating a partially indexed field add or remove it from an index in Postgres Thanks for the great answer, I'm a reluctant to accept right now though, because I've put this live and am still seeing the index still grow, despite the number of archived = false rows remaining (essentially) constant (including after a VACUUM, but not a FULL) |
|
Oct 13 |
comment |
How should we handle rows which won't be queried once they are old in PostgreSQL? Thank you for the comprehensive response and ideas. More karma up for grabs on a follow-up question. |
|
Oct 13 |
asked | Does updating a partially indexed field add or remove it from an index in Postgres |
|
Oct 13 |
accepted | PostgreSQL Index Caching |
|
Oct 5 |
asked | PostgreSQL Index Caching |
|
Oct 5 |
awarded | Scholar |
|
Oct 5 |
accepted | How should we handle rows which won't be queried once they are old in PostgreSQL? |
|
Oct 5 |
awarded | Supporter |
|
Sep 29 |
awarded | Student |
|
Sep 28 |
asked | How should we handle rows which won't be queried once they are old in PostgreSQL? |