Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
castorp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
castorp
6y ago
I was talking about a backup, not a dump (snapshot). https://blog.dbi-services.com/what-is-a-database-backup-back...
32.
▲
by
castorp
6y ago
> I know there are some ways that reduce the downtime, like hard linking the data between the clusters instead of version You need to have a proper backup of the database anyway, so I don't really see the risk in using the --link mo
33.
▲
by
castorp
6y ago
Well, there was the case where the the NSA intercepted hardware shipments (I think it was Cisco HW) to install their backdoors.
34.
▲
by
castorp
6y ago
I think you will always find something that the other product doesn't have (or doesn't have in the same way) Postgres e.g. has the infrastructure for extendable data types and index types and the infrastructure for extensions - no
35.
▲
by
castorp
6y ago
> Zheap does lead to lots of tricky scenarios. If for any reason you need to access the old copy of the row, you have to fetch it from the separate file. If the transaction that performed that update is rolled back, you need to replace t
36.
▲
by
castorp
6y ago
The SQL standard also defined an operator for that: IS DISTINCT FROM
37.
▲
by
castorp
6y ago
https://blog.sql-workbench.eu/post/epoch-mania/
38.
▲
by
castorp
6y ago
There are some areas where Oracle indeed offers more features (mainly in the administration/monitoring area) compared to Postgres, but PL/SQL vs. PL/pgSQL as a procedural language PL/pgSQL is not one of them. Both langua
39.
▲
by
castorp
6y ago
That's plain wrong. Ora is short for Oracle
40.
▲
by
castorp
6y ago
> 4. Parallel Query Execution Available since Postgres 9.6 and getting better with every release.
41.
▲
by
castorp
6y ago
> How do people keep track on all the features that are added in RDMS? By reading the release notes
42.
▲
by
castorp
6y ago
> One important point is that Uber wrote this running on Postgres 9.2. The latest Postgres release is now 12.4 Just a minor nitpick: Postgres changed the version numbering scheme with version 10. So 9.4 was a major release, but 12.4 mark
43.
▲
by
castorp
6y ago
The Postgres team decided against implementing MERGE when they designed the ON CONFLICT feature (it actually started as a MERGE). It's been a while, but as far as I remember, the main reason was that the behaviour of MERGE mandated by
44.
▲
by
castorp
6y ago
> At the end of the day, you still have to go to disk on writes, and this must be serialized against reads for basic consistency reasons. No, absolutely not. That's why modern databases use a thing called multi version concurrency c
45.
▲
by
castorp
6y ago
> Boeing will build a new version of its F-15, an older fighter jet developed in the 1960s Am I the only one that immediately thinks about the 737max disaster where they tried the same thing?
46.
▲
by
castorp
6y ago
Postgres does not support read uncommitted
47.
▲
by
castorp
6y ago
There is a built-in supported set of features for high availability. What exactly are you missing?
48.
▲
by
castorp
6y ago
I'll test it as well: - stupid dark mode: makes me cranky, gives me a headache - light mode: relaxed reading, makes me feel comfortable. - different results ever? No. the above is from the undisputed, worldwide export on what I feel.
49.
▲
by
castorp
6y ago
I absolutely hate dark mode. I even had to install a Firefox plugin to disable dark colors, to make website that use it readable again.
50.
▲
by
castorp
6y ago
The Postgres team has been using SQLSmith for that purpose for a while if I'm not mistaken.
51.
▲
by
castorp
6y ago
What's the difference between a query hint and a planner hint? > automatic planner adjustment when true cost was off More often than not, this "automatic adjustment" makes things worse. > active-active clustering with
52.
▲
by
castorp
6y ago
> Very few databases support transactional DDL Postgres, SQL Server, Firebird, DB2, SQLite, Ingres, Informix, Teradata, Vertica all support transactional DDL
53.
▲
by
castorp
6y ago
> MySQL and PG are not truly consistent per default, they don't fsync every writes. Postgres most certainly does fsync by default. It's tru, you can disable it, but there is a big warning about "may corrupt your database&q
54.
▲
by
castorp
6y ago
How does that look like with a multi-row insert?
55.
▲
by
castorp
6y ago
And when you need to insert more than one row, you repeat the column name over and over again for each row - not a good idea either.
56.
▲
by
castorp
7y ago
Are there any European hosted (and owned by a European company) alternatives to GitHub or GitLab?
57.
▲
by
castorp
7y ago
But a lot more people find loud engines simply horrible and inconsiderate.
58.
▲
by
castorp
7y ago
I was referring to the native execution using LLVM. Which should be independent of the underlying storage strategy (column-store, row-store)
59.
▲
by
castorp
7y ago
Can it do load balancing and failover?
60.
▲
by
castorp
7y ago
Well, this simply moves the problem of "commenting out" one column from the end of the list to the start of the list. I find myself doing both equally frequent.
More ›