Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ahachete
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
33 ms
·
331.
▲
by
ahachete
10y ago
Near infinite scalability with little loss of performance? Definitely not with MongoDB. Can you show that with some numbers? I have seen quite the contrary: insertion speed slightly decreases with database size. Aggregate query speed decrea
332.
▲
by
ahachete
10y ago
Have you tried pgadmin 4? It's a complete rewrite.
333.
▲
by
ahachete
10y ago
You can write a plpgsql function that returns a setof refcursor (pointer to cursors). You can then iterate these cursors to retrieve the results from an arbitrary number of tables.
334.
▲
Hadoop 3.0.0 alpha1
(hadoop.apache.org)
3 points
by
ahachete
10y ago
|
0 comments
335.
▲
by
ahachete
10y ago
I'm not Paxos expert either, but I see some issues with the current post that are probably not correct / totally precise: - That 7 or more nodes exhibit degraded performance, and that 5 is the sweet spot seems like a handy-wavy st
336.
▲
by
ahachete
10y ago
Size does matter. And there are databases which you practically can't backup logically (as you mentioned). So IMHO only applies to small databases in which case, sure, a pg_dump is always handy. But not in the rest of the cases.
337.
▲
by
ahachete
10y ago
That's true, but why would you want to run pg_dump on the instance? Use pg_receivexlog and friends to have a physical backup and pg_recvlogical for logical backups and you avoid the problem with pg_dump (you're alone with other lo
338.
▲
Heap WARM Tuples – Design Draft
(postgresql.org)
88 points
by
ahachete
10y ago
|
15 comments
339.
▲
by
ahachete
10y ago
While I mostly agree with your comment, some NoSQL databases are not suitable for analytics. Indeed, they are terrible at them. Unstructured information is, surprise, unstructured, which means it is harder to query / analyze, since the
340.
▲
by
ahachete
10y ago
We have rectified the web site. No longer says "first", just states now the fact that its open source. Thanks!
341.
▲
by
ahachete
10y ago
Right now ToroDB handles sharding at the backend (RDBMS) level, with those dbs that support that. There's currently a Greenplum-based backend on the works, that obviously handles sharding by itself. Also CitusDB is on the roadmap. At a
342.
▲
by
ahachete
10y ago
Strongly biased comment here, but hope its useful. Have you tried ToroDB ( https://github.com/torodb/torodb )? It still has a lot of room for improvement, but it basically gives you what MongoDB does (even the same API a
343.
▲
by
ahachete
10y ago
While I love seeing more PostgreSQL offerings in the cloud, I don't understand why they call it PaaS. It's a DbaaS, but a PaaS... a PaaS is really an application API that is managed by the cloud provider, and takes care of stuff l
344.
▲
by
ahachete
11y ago
You are right. If you, effectively, configure it for M responses, you get the same availability. But there are more differences between both setups: - Paxos is master-less, so you can write to any node (there's no need for a master). -
345.
▲
by
ahachete
11y ago
PostgreSQL supports synchronous replication since 9.1. What 9.6 will have is support for more than one synchronous replicated server. In any case, synchronous replication means that all of the participating servers have to participate in
346.
▲
by
ahachete
11y ago
pg_paxos should be seen as a building block for other systems/applications (like this example of a distributed execution queue). As such, and as highlighted in the post, it provides several features not present in other distributed sys
347.
▲
Master-Less Distributed Queue with PG Paxos
(citusdata.com)
99 points
by
ahachete
11y ago
|
17 comments
348.
▲
by
ahachete
11y ago
Unfortunately, UNIQUE is not enough to prevent the kind of errors I am talking about. They are only easily prevented if the PRIMARY KEY is a natural key. I have seen many cases where concepts that are UNIQUE NOT NULL for a given business ca
349.
▲
by
ahachete
11y ago
Sure, there's CASCADE, but as you pointed out it has several drawbacks. That's why ideally natural keys should be immutable. That has many advantages over surrogate keys. There's a follow up post (posts) to this presentation:
350.
▲
by
ahachete
11y ago
Do you know SSSKA? Society to Stop Surrogate Key Abuse: http://www.slideshare.net/PGExperts/keyvil-lightning-talk?qi... ;)
351.
▲
by
ahachete
11y ago
Congratulations, Citus. Since I heard last year at PgConfSV that you will be releasing CitusDB 5.0 as open source, I've been waiting for this moment to come. It makes 9.5's awesome capabilities to be augmented with sharding and di
352.
▲
by
ahachete
11y ago
ToroDB - https://github.com/torodb/torodb It's both a NoSQL and SQL database in the same place. Has the best of both worlds. Speaks the MongoDB protocol, stores the data in PostgreSQL. You no longer have to choose
353.
▲
by
ahachete
11y ago
Most of this work, and much more, including compatibility with the MongoDB protocol (including replication) is already done in ToroDB ( https://github.com/torodb/torodb ). Hope that this self-plug is hopeful :)
354.
▲
by
ahachete
11y ago
The benchmark should be re run with proper PostgreSQL configuration parameters. PostgreSQL's default configuration is very very conservative. This benchmark is like trying to see which is faster, a Ferrari or a Lamborghini, on a single
355.
▲
by
ahachete
11y ago
I have been using jOOQ for quite some time. Indeed, it's the only mechanism (definitely not an ORM) to access the database that we use in my company. From my own experience, and this is general consensus, it's a big win to use i
356.
▲
by
ahachete
11y ago
It still is "databases that do not do SQL". Having a SQL-esque query language is very far from the implications of "doing SQL": - Any external software that relies on SQL (not a similar language that looks like but it is
357.
▲
by
ahachete
11y ago
Thank you, John De Goes. I definitely agree. While PostgreSQL FDWs are a great way of extending Postgres, I don't see they are a good fit for this use case. Not only there are a lot of pushdowns not supported (although that is in the p
358.
▲
MongoDB 3.2 BI Connector is based on PostgreSQL
(docs.mongodb.org)
4 points
by
ahachete
11y ago
|
0 comments
359.
▲
by
ahachete
11y ago
It's nothing new that PostgreSQL is a great tool for doing analytics, even coming from MongoDB. I'm very happy that MongoDB took this route, it speaks a lot about their capabilities in the non-OLTP world. Having said that, I very
360.
▲
by
ahachete
11y ago
Maybe it was just me. However, if my feedback would help, I'd say that there was a lack of technical detail of the stuff mentioned. It was only covered from a superficial point of view, and many different complex issues where mentioned
More ›