ahachete

19 ms·

151.
Show HN: StackGres: open-source Postgres-aaS on Kubernetes with 120 Extensions(stackgres.io)
54 points by ahachete 5y ago|3 comments
152.
by ahachete 5y ago
OP here. Related post (and subsequent reply) from yesterday: https://news.ycombinator.com/item?id=28512274
153.
Respecting the majority, questioning the status quo as a minority(postgresql.fund)
2 points by ahachete 5y ago|1 comments
154.
by ahachete 5y ago
We (Fundación PostgreSQL) posted a new post titled "Respecting the majority, questioning the status quo as a minority": https://postgresql.fund/blog/respecting-majority-questioning...
155.
by ahachete 5y ago
> The first two organizations are almost the same thing as the core team, for all practical purposes (unless you're a lawyer, say). There is very significant overlap in membership. A cosy arrangement, certainly. I imagine that this
156.
by ahachete 5y ago
No, I mean the "rules" that would enable a NPO to be able to hold IP for the project. There are no rules for that, yet PostgreSQL Europe holds trademarks and domain names for the PostgreSQL project. And nobody has asked them, neit
157.
by ahachete 5y ago
> The correct way to go about that is not to make the holding entity and then try to surreptitiously acquire the trademark, but to have approached the community first. Did you approach the community prior to attempting to take over an as
158.
by ahachete 5y ago
> Once the problem escalates to be a legal dispute, this is the only way communication can happen. But there hasn't been any other previous communication. Our first notice from them, as detailed in the post, was from their lawyers.
159.
by ahachete 5y ago
Postgres is not only about code. It's a Community. Contributions are more than code. We value team membership by their abilities, and values. Those may prove better at building Community that C programming ability. Yet you are wrong wh
160.
by ahachete 5y ago
Sure. Fundación PostgreSQL co-founder and current President.
161.
by ahachete 5y ago
My bad. Thanks.
162.
by ahachete 5y ago
No, the Founder's are the Founding members (5). In any case, read the will: Article's 3 and 4. Do you disagree with them? Do you think they are bad for Postgres, or good? Do you support that will? Because if so, this will is a pow
163.
by ahachete 5y ago
Actually, IMHO, it's the Core team + PAC + PEU who have acted in bad faith. As the post states, with dates, there has never been any communication from them to discuss this matter. Only through laywers, since day 0. Even some of them,
164.
by ahachete 5y ago
I hope this clarifies our point: https://postgresql.fund/blog/postgres-core-team-attacks-post...
165.
by ahachete 5y ago
In Spain, a Foundation is a very strong legal entity scrutinized by the Ministry of Justice. This means, among other things, that: * Every action of its board is supervised by the Ministry of Justice. * No action or change to the status can
166.
by ahachete 5y ago
Rubén J. Bravo, Manuel Argiz, César Calvo Pinilla, Alberto Picón and myself.
167.
by ahachete 5y ago
I agree that we need to enhance the website and give more visibility to the people behind the foundation. We will do so shortly. Yet this is public (as in the public registries). Please contact us if you want further information.
168.
by ahachete 5y ago
This is a response to https://news.ycombinator.com/item?id=28512274 OP here.
169.
by ahachete 5y ago
Fundación PostgreSQL is a 100% independent non-profit organization not tied to any company or any other institution. Its governing board cannot have more than 40% members of the same company. Please go to https://postgresql.fund&
170.
by ahachete 5y ago
Leaving aside considerations about my person, here's Fundación PostgreSQL's response and HN discussion thread: https://news.ycombinator.com/item?id=28514422
171.
Postgres Core Team launches unprecedented attack against the Postgres Community(postgresql.fund)
22 points by ahachete 5y ago|9 comments
172.
by ahachete 5y ago
If using SSD or similar fast storage subsystem, or those that hide a higher random access time vs sequential, you may indeed want to reduce random_page_cost to make random_page_cost / seq_page_cost in the 1.2-1.5 range. But it's a
173.
by ahachete 5y ago
Fair enough. Yet it might be difficult to summarize the tradeoffs succinctly enough for a title. "Harmful" conveys enough information to raise awareness of a topic which might not be usually considered. Both examples show this pat
174.
by ahachete 5y ago
That they are hyperbolic, maybe. I disagree with the rest, I believe there are tons of information on both examples about why they are harmful. (edit, typo)
175.
by ahachete 5y ago
I'm the co-author of one of such ones: "Schema Later Considered Harmful" [1]. I don't see what's wrong with this "type titles", may you elaborate? :) [1] https://www.enterprisedb.com/blog&#
176.
by ahachete 5y ago
This is a deep and excellent post. Thanks for publishing it and all the research required. Maybe too much 30,000 feet perspective, but in general everything that is "state" in a session is a potential limit to performance and scal
177.
by ahachete 5y ago
> Why have the RDBMS as the default? It's possibly the sanest default for a data persistence layer. I'd argue otherwise: use a RDBMS unless you know what you are doing. > the number of web applications that make effective us
178.
by ahachete 5y ago
Before thinking of removing the RDBMS; replacing itwith a NewSQL/NoSQL; or trying to horizontally shard, ask yourself: what is the performance I really need? * Read-only queries can easily be scaled out to read replicas. * Write transa
179.
by ahachete 5y ago
We created https://postgresqlco.nf which not only offers detailed help about all configuration parameters, but also provides a "repository" for you to upload/download your Postgres configurations, and a Tuning Gui
180.
by ahachete 5y ago
The AGPL is a free software license. This implies that guarantees the well-known freedoms. Among them, there is the freedom to modify software for your own use. As long as you don't exposed this modified version of a hypothetical AGPL-

More ›