bonesmoses

5 ms·

1.
by bonesmoses 3mo ago
Postgres 19 is looking to be a solid release. I don't think I've seen this much "new" stuff in a single version since v10 came out.
2.
by bonesmoses 3mo ago
Awesome! I'll look forward to that. :)
3.
by bonesmoses 11mo ago
Version 3.6 is definitely after we introduced that functionality. It was, alas, rarely deployed though. Usually clients needed a consultant to put together a configuration for them, and most didn't bother.
4.
by bonesmoses 11mo ago
There's an option in the Postgres configuration named "track_commit_timestamp" that does this automatically. It's required to be enabled when using LWW as the conflict resolution model. If there's a tie, the node wi
5.
by bonesmoses 11mo ago
I don't recall which customer you may have been, but the standard solution to that specific DDL issue with BDR is to use Stream Triggers to enable row versioning. One of the 2ndQuadrant customers used it extensively for multi-region cr
6.
by bonesmoses 11mo ago
You can't even run pgbench unaltered on CockroachDB, as simple table structures and indexes are fundamentally different there. It is in no way a compatible product, and never has been.
7.
by bonesmoses 11mo ago
In Postgres, updates contain the entire row, including all column values. Since the Spock extension follows the "Last Write Wins" model by default, one row version will win, while the other is essentially discarded. This is assumi
8.
by bonesmoses 2y ago
I'm not against using UUIDs, but it has to be done in a balanced manner. Normal numeric IDs for all surrogates, and then a UUID as an external lookup attribute. You push that externally for API calls, tokens, etc. so you don't hav
9.
by bonesmoses 5y ago
You might want to consider a different name, as there's already a pgcat project which appears to be a logical replication extension to augment native logical replication. https://github.com/kingluo/pgcat
10.
by bonesmoses 7y ago
Right tool for the right job. Users in Tokyo won't be editing accounts for users in Austrailia. There's often a natural partition there where you can leverage the data locality with an eventual consistency basis safely. Conflict-f
11.
by bonesmoses 7y ago
LWW / LUW systems are a fine first approximation, but generally do not fulfill the strictest guarantees and desirable outcomes for a database without accounting for a lot of edge cases. A good conflict management system will have that
12.
by bonesmoses 8y ago
I had a very protracted DPDR experience start around when I was 12, and slowly dissipated over the course of a decade. I woke up one morning, and it was like I was slapped out of my body. It's like I was piloting a Me(ch) suit. I wasn&
13.
by bonesmoses 8y ago
Just the annoyance of having to itemize a receipt _to that granularity_ would annoy me enough to quit working at a company like that.
14.
by bonesmoses 9y ago
That's an excellent point. By opening up this can of worms, MySQL fans essentially get free reign to take shots at Postgres for flaws it still has for one reason or another. Perceived or genuine. On the other hand, sometimes a good fla
15.
by bonesmoses 9y ago
Cross-column statistics are one of my favorites. The way Postgres 10 handles it is really a _huge_ advancement that addresses a painful edge case that has been around for ages. https://blog.2ndquadrant.com/pg-phriday-crazy-c
16.
by bonesmoses 9y ago
So far as the speed is concerned, we ran some tests a while back and it came back as nearly native performance when compared to interacting with a non-partitioned table: https://blog.2ndquadrant.com/pg-phriday-dearly-de-part
17.
by bonesmoses 10y ago
Which is, almost ironically, going back to vocational training instead of standard Liberal Arts degrees. I triple-majored in Math, Physics, and Computer Science because I had to be there for the whole degree, so why not. But all I really n
18.
by bonesmoses 10y ago
As someone who went to that Cornell, I somewhat regret my decision. Sure you can cram in as much information as possible in that month, but long-term memory generally requires periodic refreshes. I've forgotten pretty much everything I
19.
by bonesmoses 10y ago
Isn't 30% is more than enough? If 3-4 people apply for a single position and 1-2 of them have a degree, then it's a fairly reasonable decision to ignore the other two. And the ratios I've seen are far more than 3-4 applicatio
20.
by bonesmoses 10y ago
Is it really a "reverence" though? When practically everyone and their dog has one, it's the new minimum.
21.
by bonesmoses 10y ago
This is in very specific neighborhoods due to gang activity for the most part. It's hardly an indicator of safety over the city in general.
22.
by bonesmoses 10y ago
I'm not entirely certain normalizing hyperbole makes sense here. There's a massive difference between ensuring children are safe and supported, and never letting them do anything without supervision or face any consequences up t
23.
by bonesmoses 10y ago
That may be the case, but they need to update the documentation to reflect that. This is what it currently says: "Note: All the new features required have been submitted for inclusion in PostgreSQL 9.5. Many have already been accepted
24.
by bonesmoses 10y ago
Citus currently has major problems joining non-distributed tables with distributed tables, and it doesn't fully support schemas yet. It's almost there, but not quite.
25.
by bonesmoses 10y ago
Very informative. Thanks!
26.
by bonesmoses 10y ago
The first was performance, while the second is a 500TB database, and that very much requires scaling. I'm just saying it can do both well.
27.
by bonesmoses 10y ago
In Postgres, because it uses MVCC, every count requires verifying the table row in the data segment. This means a sequential scan over the contents of the table to verify the rows exist and are visible to the current session. Few operations
28.
by bonesmoses 10y ago
Exactly. With Postgres, you can add CHECK constraints to enforce specific keys, with any level of nesting desired. So an INSERT could reject a document for having missing fields, fields of improper type, etc. It all depends on how strict yo
29.
by bonesmoses 10y ago
Could you explain a bit more about this? From what I can see, it's just journal consumption. That's basically how Postgres does it, too.
30.
by bonesmoses 10y ago
It may or may not be apt, but it just felt like I was dumping JSON objects wherever, with a loosely applied path of db.collection to keep things together.

More ›