I voted to re-open this because the OP has made the asked-for changes to their question. I'd answer it, but I don't know enough about indexing in PostgreSQL to be of real help.
@MaxVernon It still remains unclear, in my view. How does an ER model for a single table differs from that table itself? What does it have to do with indexing in general and Postgres in particular?
@mustaccio I agree it's not a perfect question, I just didn't want the OP, after they've updated the question several times, to lose patience with us. Just trying to be as welcoming as possible. It seems to me, someone could provide a CREATE TABLE statement with likely helpful indexing for the scenarios they've presented in their question.
I think i understand the question now. OP is looking for a database diagram to represent the table he/she/they/x are showing in the example. Some form of normalised database design to import that data.
I am using this statement to get all the rows ordered by timestamp in ascending order
DELETE FROM @tableName
WHERE id = ANY (
SELECT id
FROM @tableName
WHERE source = :p1 AND target = :p2 @readCondition
ORDER BY createddate
LIM...
A few minutes ago, new Post Notices was launched across the Stack Exchange network. This includes all public sites, all meta sites, and all Basic and Business tier Teams (Enterprise tier will get it in a future release).
For our purposes, a 'post notice' includes any status banner shown on quest...
> Please clarify your specific problem or add additional details to highlight exactly what you need.
> Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer.
These two sentences are opening sentences from two close reasons' descriptions. To me they look almost completely interchangeable
The word "limit" kind of prevents the second one from being used instead of the first one, but you can still substitute the first one for the second one.
Oh, and closed questions used to be shown as 'on hold' for the first five days, both in the title and in the notification box. Apparently we are now back to the old terminology, which means they are 'closed' straight away.
@PaulWhitesaysGoFundMonica To be serious for a second, I actually don't have an opinion on that either way. But it's a curious change, because I remember that the 'on hold' thing was sold at the time as one way to be friendlier to newcomers.
I am using this statement to get all the rows ordered by timestamp in ascending order
DELETE FROM @tableName
WHERE id = ANY (
SELECT id
FROM @tableName
WHERE source = :p1 AND target = :p2 @readCondition
ORDER BY createddate
LIM...
