StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2522523
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-26T10:34:37.610
FavoriteCount
0
LastActivityDate
2010-03-26T10:34:37.610
LastEditDate
LastEditorUserId
0
OwnerUserId
247256
ParentId
205324
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
As highlighted above the problem is not with the particular database you are using, i.e. PostgreSQL but one of the following: <ul> <li>Schema design, maybe you need to add, remove, refine your indexes</li> <li>Hardware maybe you are asking to much of your server - you said 5k users but then again very few of them are probably querying the db at the same time</li> <li>Queries: perhaps poorly defined resulting in lots of inefficiency</li> </ul> A pragmatic way to find out what is happening is to analyse the PostgeSQL log files and find out what queries in terms of: <ul> <li>Most frequently executed</li> <li>Longest running</li> <li>etc. etc.</li> </ul> A quick review will tell you where to focus your efforts and you will most likely resolve your issues fairly quickly. There is no silver bullet, you have to do some homework but this will be small compared to changing your db vendor. Good news ... there are lots of utilities to analayse your log files that are easy to use and produce easy to interpret results, here are two: <a href="http://pgfouine.projects.postgresql.org/" rel="nofollow noreferrer" title="pgFouine - a PostgreSQL log analyzer">pgFouine - a PostgreSQL log analyzer (PHP)</a> <ul> <li><a href="http://pgfouine.projects.postgresql.org/reports/sample_default.html" rel="nofollow noreferrer">pgFouine: Sample report</a></li> </ul> <a href="http://pqa.projects.postgresql.org/" rel="nofollow noreferrer" title="Practical Query Analysis">PQA (ruby)</a> <ul> <li><a href="http://pqa.projects.postgresql.org/example.html" rel="nofollow noreferrer">PQA: Sample report</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POwhich db should i select if performance of postgres is low
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USbelvoir
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.