franckpachot

6 ms·

1.
AI-Powered Retrieval in PostgreSQL with Azure HorizonDB(techcommunity.microsoft.com)
2 points by franckpachot 2mo ago|0 comments
2.
by franckpachot 3mo ago
And: > The instance was assigned a public IP I think that without a private link, the managed services that run in different accounts (Neon, Crunchy, Clickhouse if not BYOL) may be in a different data center than the client's. And t
3.
by franckpachot 3mo ago
"dollar quoting" is the PostgreSQL way to quote strings with quotes, avoiding double quoting or escape characters. I like to use the tagged version of it, like $sql$ SELECT ... $sql$ to describe what is inside.
4.
by franckpachot 9mo ago
Beyond the hype, the PostgreSQL community is aware of the lack of "batteries-included" HA. This discussion on the idea of a Built-in Raft replication mentions MongoDB as: >> "God Send". Everything just worked. Repl
5.
by franckpachot 9mo ago
Be sure to read the Муths and Truths about Synchronous Replication in PostgreSQL (by the author of Patroni) before considering those solutions as cloud-native high availability: https://www.postgresql.eu/events/pgconfde
6.
by franckpachot 9mo ago
CloudNativePG is automation around PostgreSQL, not "batteries included", and not the idea of Kubernetes where pods can die or spawn without impacting the availability. Unfortunately, naming it Cloud Native doesn't transform a
7.
by franckpachot 9mo ago
It's largely cultural. In the SQL world, people are used to accepting the absence of real HA (resilience to failure, where transactions continue without interruption) and instead rely on fast DR (stop the service, recover, check for da
8.
Rethinking Data Integrity: Why Domain-Driven Design Is Crucial(thenewstack.io)
2 points by franckpachot 9mo ago|0 comments
9.
by franckpachot 9mo ago
What about "cannot scale without downtime"? While all databases can scale vertically, increasing or decreasing CPU or memory resources requires a restart, which leads to downtime. All sessions must disconnect, the system restarts,
10.
Why 'Store Together, Access Together' Matters for Your Database(thenewstack.io)
1 points by franckpachot 10mo ago|0 comments
11.
by franckpachot 1y ago
What is the null join behavior that cause you problem?
12.
by franckpachot 1y ago
The companies that attempt to replace PostgreSQL do so not to replace PostgreSQL itself, but to replace Oracle.
13.
by franckpachot 1y ago
Can you provide more details? Inserting with unique indexes do not lock the table. Case statements are ok in where clause, use expression indexes to index it
14.
by franckpachot 1y ago
A Data Council talk on the modern SQL vs NoSQL
15.
by franckpachot 1y ago
The Write-Ahead Logging (WAL) is single-threaded and maintains consistency at a specific point in time in each instance. However, there can be anomalies between two instances. This behavior is expected because the RDS Multi-AZ cluster does
16.
by franckpachot 1y ago
Do you declare your Foreign Key in your SQL database? What about MongoDB?
17.
by franckpachot 2y ago
Are NULLs treated as distinct or duplicates in your UNIQUE INDEX? It depends SQL != NoSQL != some specific implementations Which option offers the best developer experience? Comments welcome
18.
by franckpachot 2y ago
YugabyteDB supports much more than basic things. I've been a 3+ years dev advocate for Yugabyte, and I've always seen triggers. LISTEN/NOTIFY is not yet there (it is an anti-pattern for horizontal scalability, but we will add
19.
by franckpachot 2y ago
Index creation should not be controlled by statement timeout, but backfill_index_client_rpc_timeout_ms which defaults to 24 hours. May have been lower in old versions
20.
by franckpachot 2y ago
It depends on the use cases and performance goals. You may want to distribute the rows that you insert, and then a random UUID makes sense. However, it is too much distributed for B-Tree indexes and the problem is not only cache but the amo
21.
by franckpachot 2y ago
1. Regarding performance, I recently did a simple test. CockroachDB uses a considerable number of CPU instructions compared to YugabyteDB: https://dev.to/yugabyte/comparing-sql-engines-by-cpu-instruc... Writing a datab
22.
by franckpachot 2y ago
YugabyteDB is and will always be Apache2. It is PostgreSQL compatible (the query layer is a fork of PostgreSQL) so the migration from CockroachDB, which implements a subset of PostgreSQL features, is easy.
23.
How to Enhance Database Performance Testing Using Custom SQL Scripts in PgBench(yugabyte.com)
10 points by franckpachot 2y ago|0 comments
24.
Advanced PostgreSQL Partitioning by Date with YugabyteDB Auto Sharding(yugabyte.com)
12 points by franckpachot 2y ago|0 comments
25.
by franckpachot 2y ago
What I do not understand is they say "we explored CockroachDB, TiDB, Spanner, and Vitess". Those are not compatible with PostgreSQL beyond the protocol and migration would require massive rewrites and tests to get the same behavio
26.
by franckpachot 2y ago
Maybe it is not the planner. On difference between those other databases and PostgreSQL is that their plan do not depend on how freshly the table was vacuumed. The cost of your "correct index" may becomes worse when the rows are u
27.
by franckpachot 2y ago
In all databases you will avoid bad plans (and the unpredictable performance related to plan changes) by providing the right index. You have two selective filters: WHERE and LIMIT so the right index have both
28.
by franckpachot 3y ago
If changing random_page_cost from 4 to 2 makes a difference, then probably there are no good indexes. The choice between Seq Scan and Index Scan should be obvious without depending on small adjustments or one day, with slightly different da
29.
by franckpachot 3y ago
Even if bugs are fixed instantly, nobody will apply a patch in production withiut previous testing. Changing system-wide behavior to fix a single query may make things worse. Hints are the only way to fix at the scope of one statement with
30.
by franckpachot 3y ago
All those methods are try and guess. With hints you can have a scientific approach to understand why the bad plan has been chosen and find the right plan. Then, you can address the root cause. join_collapse_limit=1 may set the join order bu

More ›