| bio | website | |
|---|---|---|
| location | Barcelona, Spain | |
| age | 33 | |
| visits | member for | 1 year, 8 months |
| seen | May 6 at 11:56 | |
| stats | profile views | 14 |
|
Sep 30 |
answered | Database schema - performance v correctness information |
|
Sep 17 |
awarded | Yearling |
|
Jun 17 |
answered | Transferring Data from one table to another |
|
Jun 1 |
awarded | Scholar |
|
Jun 1 |
accepted | Migrating and normalizing data |
|
May 31 |
awarded | Student |
|
May 31 |
comment |
Migrating and normalizing data Oh, I do use surrogates in the new app. I thought I'd use new ones. But that's probably not very useful... |
|
May 31 |
asked | Migrating and normalizing data |
|
Mar 27 |
answered | Storing Changes To Records |
|
Jan 28 |
answered | I have lots of free memory. How do I use it to increase performance? |
|
Jan 23 |
awarded | Tumbleweed |
|
Jan 16 |
asked | Working across multiple PostgreSQL database servers |
|
Dec 28 |
comment |
MySQL Sharding tables/servers or other methods to reduce table sizes? You rarely have control over caching (IIRC, Oracle has this using keep/recycle pools), and I don't think you'll need it- if you have proper indexes, caching will work just fine. If you only do queries with exact matches on two columns, an index for each column will likely yield excellent performance. In any case, I suggest you build a test server (a 4Gb box should be pretty cheap), create a load test (this should be easy given your usage patterns) and try different indexing and configuration options and measure improvements to your load test. |
|
Dec 28 |
answered | MySQL Sharding tables/servers or other methods to reduce table sizes? |
|
Dec 28 |
awarded | Critic |
|
Dec 28 |
comment |
postgresql view with max min with id Don't worry! I'd suggest you go with Erwin's answer, and only go this way if somehow Erwin's answer can't be made to run as fast as you need |
|
Dec 27 |
comment |
postgresql view with max min with id Are they? I thought each RDBMS used different syntax. If it is, it boggles my mind that limit/offset is not standardized (which it wasn't last time I checked, IIRC- although that was ages ago). |
|
Dec 27 |
comment |
postgresql view with max min with id I've upvoted yours. I propose this solution and keep it here 'cause window functions are not widely available in all RDBMSs, nor standardized, and because they might be less performant. However, I'll edit a bit my answer... |
|
Dec 27 |
answered | postgresql view with max min with id |
|
Dec 27 |
awarded | Citizen Patrol |