sorkin2

4 ms·

1.
by sorkin2 9y ago
While admittedly this could be seen as a mistake in SQL, you can differentiate by looking at whether b.id is NULL or not.
2.
by sorkin2 9y ago
That's a "cure" worse than the disease.
3.
by sorkin2 9y ago
What kind of official support?
4.
by sorkin2 9y ago
Tough.
5.
by sorkin2 9y ago
The same way the new built-in logical replication works: logical decoding.
6.
by sorkin2 9y ago
Really hasn't been in years. I've not even heard of anyone using it in over a year. But I mostly speak with people who stream video games.
7.
by sorkin2 9y ago
> One kind of significant downside of partial indexes in PostgreSQL is that they don't work with parameters. Your example is fundamentally different from parameters sent by a client in a parameterized query, i.e. $1, $2, etc. Also
8.
by sorkin2 9y ago
> Changing from master to replica is easy, but now you have to rebuild that original master off of the former replica now. Completely start over. You can't just start up again from a given transaction ID. MySQL's GTID implement
9.
by sorkin2 10y ago
> They maintained a replication process across both tables as they updated the read processes before updating the write process. Say for whatever reason their offline replication process broke for 2 hours. From the article I got the impr
10.
by sorkin2 10y ago
This kind of nannying can be really expensive to do correctly when trying to build high performance systems -- to the point where it doesn't make sense to punish everyone just because someone who didn't read the manual MIGHT misus
11.
by sorkin2 10y ago
Hmm.. So was there a workflow where I could say "I'd like for this not to be pushed until I've approved it", even if the patch is assigned to be reviewed by someone else? Of course, I could just comment with that on th